Professional Website Review

Tide & Hive

tideandhive.com
Reviewed by
Marcus Knapman
Studio
Exmoorweb Website Design
Date
02 April 2026
Industry
E-commerce · Beauty · Skincare
7.5 / 10 Overall

Executive Summary

Tide & Hive has a fantastic digital foundation. The site is professionally executed, the storytelling is compelling, and the niche—luxury, natural anti-ageing skincare—is well-defined. It doesn’t feel like a template; it feels like a bespoke brand with a clear vision. However, the WordPress and Elementor platform is introducing unnecessary technical debt, and with the site still in a “Coming Soon” phase, now is the ideal time to migrate to a hand-coded, performance-first build before the full commercial launch.

4
Pages
115 KB
HTML Weight
36
CSS Files
22
JS Files
1
Product
0
Active Checkout

Target Audience & Market Position

Who this brand is speaking to, and how effectively the site reaches them.

🎯

Primary Demographic

Women aged 35–60+ who are invested in premium skincare and actively seek natural, non-synthetic alternatives. The anti-ageing messaging and luxury price point naturally filter towards this bracket.

🌱

Values-Driven Buyers

Consumers who care about sustainability, provenance, and ethical sourcing. The Māori partnership story and the “science of nature” narrative directly resonate with this growing segment.

🎁

Gift Purchasers

The premium positioning and “luxury hand cream” branding make this a strong candidate for gifting. With packaging set to evolve, the site should be ready to showcase new product presentation. Currently there are no gift sets, no gifting language, and no seasonal prompts.

📱

Mobile-First Shoppers

The site is responsive and performs well on mobile. However, the lack of a working cart means mobile visitors from social media ads—the most likely discovery channel—currently hit a dead end.

Age Range Observation

While the product’s anti-ageing benefits naturally appeal to women 40+, the site’s visual language (clean, modern, Instagram-ready) skews younger than the typical anti-ageing market. This is actually a strength—it avoids the clinical or “old-fashioned” aesthetic that plagues many age-related skincare brands. That said, the font sizes and touch targets should be reviewed with older users in mind. A slightly larger body font (18–19px) and more generous button padding would improve usability for the 55+ demographic without compromising the modern feel.

Detailed Assessment

Scored analysis across four key disciplines.

01

UX & Usability

7.5 / 10

The About Us page is where this site really shines. It follows a strong narrative structure: identifying a problem (synthetic chemicals), introducing the founder (Richard), and explaining the “science of nature.” Using the founder’s story is a brilliant move—in a world of faceless Amazon brands, Richard’s background as a beekeeper adds authentic human value.

Navigation & Flow

The four-page structure (Home, Shop, About Us, Contact) is clean and intuitive. However, the Shop page currently serves as a placeholder, and there is no direct checkout or product filtering. Directing customers to Amazon is a smart, low-friction launch strategy, but the site will need a bespoke e-commerce integration—built into a custom PHP/Laravel backend—to mature commercially and own the customer relationship.

Mobile Experience

The site is responsive and clean across devices. The “Nature Fact” callouts engage users without being salesy, which is particularly effective on smaller screens where attention is fleeting.

02

Visual Design

9.0 / 10

From the moment you land on the site, the “Hive to Shore” concept is clear. The branding is sophisticated—the wave-and-hive logo is a clever piece of design that immediately communicates the product’s dual-source ingredients: Royal Jelly and Seaweed.

Brand Consistency

The colour palette (soft peach, muted gold, deep navy) and imagery lean heavily into the “luxury natural” market. It avoids the cluttered look of many startup skincare sites, opting instead for high-quality photography and plenty of white space, which builds instant trust with the consumer. Decorative touches—the honeycomb textures, wave overlays, and bee motifs—reinforce the brand story without overwhelming the content.

Typography

The custom “Boardwalk Avenue” serif typeface paired with “Outfit” for body text creates a refined typographic hierarchy that feels premium and intentional. The overall aesthetic is that of a bespoke brand, not a template.

03

SEO & Accessibility

5.5 / 10

The site is currently in a “Coming Soon” phase, which inherently limits its search visibility. While the pages are technically clean and responsive, there are meaningful gaps in the SEO and accessibility foundations that should be addressed before the full commercial launch.

SEO Observations

There is no visible blog, resource hub, or long-tail keyword strategy in place. Meta descriptions and structured data markup need attention—particularly for product pages once the shop goes live. A physical UK business address is also absent, which weakens local SEO potential.

Accessibility & Trust Signals

Image alt text is present but could be more descriptive for screen readers. Social proof elements (lab results, certifications, verified reviews from a third-party source) in the footer would further solidify the brand’s legitimacy and improve trust signal coverage.

04

Technical Strategy

5.5 / 10

The site is built on WordPress with Elementor Pro and a child theme of Hello Elementor. For a brand-building landing page, this was a reasonable starting point. However, the platform is now the site’s biggest liability as it prepares for commercial launch.

WordPress Limitations

The homepage loads 36 CSS files and 22 JavaScript files—the majority from Elementor, WooCommerce, and their dependencies. This is excessive for a four-page site with no active shop. WordPress and Elementor introduce layers of abstraction (page builders, shortcodes, database-driven templates) that constrain performance, complicate customisation, and create ongoing maintenance and security overhead. Plugin updates, theme conflicts, and database bloat will only worsen as the site grows.

Recommendation: Custom Build

For a premium brand with a focused product range, our strong recommendation is to migrate away from WordPress entirely. A hand-coded PHP/HTML/CSS/JS site—or a structured framework like Laravel—would deliver dramatically better performance, complete design control, tighter security, and a codebase that can be precisely tailored to Tide & Hive’s needs. This is not a luxury; for a brand at this stage, it is the most commercially sound technical decision.

Overall Score

7.5 / 10

Tide & Hive has built a genuinely impressive brand presence for an early-stage skincare company. The visual identity is best-in-class for its market, the storytelling is authentic and compelling, and the brand positioning is exceptionally well-defined. However, the WordPress and Elementor foundation is already straining under the weight of unused plugins and excessive asset loading—and it will only become a greater liability as the site moves towards full e-commerce. Our primary recommendation is a platform migration to a hand-coded PHP/HTML/CSS/JS build (with Laravel as a strong option), delivering the performance, security, and design control that a premium brand of this calibre deserves. Combined with a direct checkout, proper legal compliance, and the content strategy outlined in this report, Tide & Hive has every ingredient it needs to become a formidable digital presence in the luxury natural skincare space.

What a Hand-Coded Site Would Fix

The scan results below are from the current WordPress + Elementor build. Every area scoring below 90 has specific, solvable issues that a custom PHP/HTML/CSS/JS build would address directly. Here’s a side-by-side comparison of the current state versus what’s achievable.

Current WordPress Site With Hand-Coded Rebuild

Performance

75 / 100
  • Page loads in 1.04s—sluggish for a 4-page brochure site
  • 115.7 KB HTML payload (Elementor injects bloated markup)
  • 36 CSS files and 22 JS files loaded on every page
  • WooCommerce assets loading despite no active shop

With Custom Build

95+ target
  • Sub-500ms loads with clean, minimal HTML output
  • Single optimised CSS file (~15 KB) and minimal JS
  • Zero unused plugin/framework assets
  • HTTP/2 server push and aggressive caching for static assets
  • Lean markup = better Core Web Vitals (LCP, CLS, INP)
🔍

SEO

75 / 100
  • No sitemap.xml—Google can’t efficiently crawl the site
  • 6 of 11 images (55%) missing alt text
  • No analytics tracking detected
  • Structured data present but limited to a single JSON-LD block
  • Heading hierarchy includes an H3 used for a banner (semantic error)

With Custom Build

95+ target
  • Auto-generated sitemap.xml from a simple PHP script or route
  • Enforced alt text on all images via templating discipline
  • Analytics (GA4 or Plausible) baked into the base template
  • Rich structured data: Product, Organisation, BreadcrumbList schemas
  • Clean, semantic heading hierarchy with no builder-generated conflicts
  • Full control over canonical URLs, meta tags, and Open Graph per page
📱

Mobile

85 / 100
  • Fixed pixel width detected (1118px)—risks horizontal scrolling
  • Elementor responsive breakpoints are limited to predefined widths
  • Touch targets rely on Elementor’s default button sizing

With Custom Build

98+ target
  • Fully fluid layouts using modern CSS (clamp, container queries)
  • No fixed pixel widths—every element scales naturally
  • Custom touch targets sized for the 45+ demographic (min 48×48px)
  • Mobile-first CSS architecture—optimised for the most common viewport first
🔒

Security

67 / 100
  • Missing X-Content-Type-Options header
  • Missing X-Frame-Options header
  • Missing X-XSS-Protection header
  • Missing Strict-Transport-Security (HSTS)
  • Missing Content-Security-Policy
  • WordPress login page exposed at /wp-admin
  • Plugin update cycle creates ongoing attack surface

With Custom Build

95+ target
  • All security headers configured in .htaccess or server config from day one
  • No public admin panel to attack—zero WordPress/plugin vulnerability surface
  • Content-Security-Policy tailored to only allow trusted scripts and styles
  • HSTS with preload for enforced HTTPS
  • No database layer for brochure pages = no SQL injection risk
  • If using Laravel: built-in CSRF protection, rate limiting, and input sanitisation

Accessibility

75 / 100
  • 6 images (55%) missing alt text
  • Elementor-generated markup includes non-semantic wrappers
  • Heading hierarchy broken by builder layout decisions (H3 before H2)
  • Form labels and ARIA attributes depend on plugin implementation

With Custom Build

95+ target
  • 100% alt text coverage enforced through template structure
  • Clean semantic HTML5: header, nav, main, section, article, footer
  • Correct, logical heading hierarchy authored directly in markup
  • ARIA landmarks and roles applied precisely where needed
  • Keyboard navigation tested and guaranteed for all interactive elements
  • WCAG 2.1 AA compliance built in from the start, not retrofitted

Content & Extras

90 / 100
  • Good content depth (3,324 words) and structured data present
  • No analytics tracking—no visibility on visitor behaviour
  • Social links present but one is broken (http://f/)
  • Call-to-action content exists but points to a dead shop page

With Custom Build

98+ target
  • All existing content preserved and enhanced with better markup
  • Analytics integrated at template level—every page tracked from launch
  • Social links validated and managed in a single config file
  • CTAs wired to a working checkout or pre-launch email capture
  • Blog/journal system built with clean URLs and automatic RSS feed

Issues & Bugs Found

Specific technical and content issues identified during the review, graded by severity.

High

No Privacy Policy Page

The footer links to a Privacy Policy page, but the URL returns a 404 error. This is a legal requirement under UK GDPR and PECR, especially with a contact form collecting personal data. This must be resolved before any commercial launch.

High

Shop Page Is Non-Functional

The Shop link in the main navigation leads to a “Coming Soon” placeholder. WooCommerce is installed but dormant. Visitors arriving via search or social expecting to buy will bounce immediately. If the shop isn’t ready, consider removing it from the nav and adding a waitlist instead.

Medium

Heading Capitalisation Bug

The “Our Story” section heading renders as oUR sTORY—a CSS text-transform conflict with the Elementor editor. This is visible on the homepage and looks like a production error that undermines the premium feel of the site.

Medium

Excessive Asset Payload

The homepage loads 36 CSS files and 22 JavaScript files. The majority are Elementor and WooCommerce defaults—unnecessary overhead for a four-page site with no active shop. This level of asset bloat is inherent to the WordPress + page builder architecture and is a primary reason to consider migrating to a hand-coded solution where every file serves a purpose.

Medium

Twitter Card Author Leak

The Twitter meta tag twitter:data1 displays the developer email info@inventis.co.uk as the article author. This should be updated to the brand name or founder’s name for professional consistency in social sharing.

Low

“Join the Hive” Link Broken

The social media CTA “Join the Hive” links to http://f/—a placeholder URL that was never updated. This should point to the brand’s Facebook or Instagram profile.

Low

Banner Bar Phrasing

The persistent top banner reads “This website will go live very soon…” and is set as an H3 heading, which is semantically incorrect for a promotional banner and may confuse screen readers and search crawlers.

Low

No Standard Favicon Tag

While a msapplication-TileImage meta tag exists, there is no standard <link rel="icon"> tag, meaning some browsers may not display the favicon correctly in tabs and bookmarks.

Quick Wins

Low-effort, high-impact changes that can be implemented immediately.

Fix the “oUR sTORY” Heading

Correct the CSS text-transform conflict in Elementor so the heading displays as “Our Story” as intended.

5 min fix

Add a Privacy Policy

Use a UK GDPR-compliant template and publish immediately. The contact form is already collecting data without one.

1 hour

Fix Broken Social Link

Update the “Join the Hive” placeholder URL to the actual Facebook or Instagram profile.

2 min fix

Update Twitter Meta Author

Change the twitter:data1 value from the developer’s email to “Tide & Hive” or “Richard Unwin.”

2 min fix

Increase Body Font Size

Bump the base font from 17px to 18–19px for improved readability, especially for the 45+ target demographic.

5 min fix

Add Standard Favicon Tag

Add a <link rel="icon"> alongside the existing tile image meta for consistent browser tab display.

2 min fix

Recommendations

Specific, actionable steps to elevate Tide & Hive’s digital presence.

  1. Migrate Away from WordPress to a Custom-Built Site The current WordPress + Elementor stack loads 36 CSS and 22 JS files for a four-page site, introduces ongoing plugin maintenance and security risks, and constrains design flexibility. We recommend a full migration to a hand-coded PHP/HTML/CSS/JS website, with Laravel as a strong framework option for the e-commerce backend. This delivers dramatically better performance (sub-second page loads), complete control over markup and design, a significantly reduced attack surface, and a codebase that can be precisely tailored as the brand scales. The existing visual identity and content can be faithfully preserved—and improved—in the migration.
  2. Integrate a Direct E-commerce Checkout As part of the platform migration, build a bespoke checkout flow using Stripe or a similar payment gateway integrated directly into the new site. Owning the checkout will increase margins, capture customer data for remarketing, and enable subscription models and upselling—none of which are possible while relying on the current Amazon redirect strategy.
  3. Add Local SEO & Trust Signals Include a physical UK business address, company registration number, and third-party certifications (e.g. cruelty-free, organic) in the site footer. These signals are critical for building consumer trust and improving search rankings in the beauty and wellness vertical.
  4. Implement an Email Capture Strategy Add a prominent “Notify Me” or newsletter signup, ideally with an incentive (first-order discount or samples). The site is currently losing potential customers who visit during the pre-launch phase with no mechanism to re-engage them.
  5. Build a Content & SEO Foundation Introduce a blog or “Journal” section with articles on skincare science, ingredient sourcing, and Richard’s beekeeping journey. This will drive organic traffic, support long-tail keywords, and reinforce the founder-led brand narrative.
  6. Strengthen Accessibility & Performance Auditing A platform migration is the ideal opportunity to build accessibility in from the ground up. Ensure WCAG 2.1 AA compliance, semantic HTML, descriptive image alt text, and full keyboard navigability across all interactive elements. With a hand-coded site, achieving perfect Lighthouse and Core Web Vitals scores becomes realistic rather than aspirational.
  7. Expand Social Proof & Reviews The existing testimonial carousel is a good start, but integrating verified third-party reviews (Trustpilot, Feefo) and showcasing lab testing results or dermatological endorsements will significantly boost conversion rates as the site moves to direct sales.
  8. Introduce a Gifting Strategy The luxury positioning makes Tide & Hive a natural gift product—and with new packaging on the horizon, this is the ideal moment to build gifting into the site from day one. Add dedicated gifting language, seasonal bundles, and a “Gift This” option at checkout. Consider gift wrapping as an upsell—this is a proven revenue driver in the premium skincare market.
  9. Optimise for the 45+ Demographic While the visual design is modern and appealing, the primary buyer for anti-ageing hand cream is likely 45–65+. Increase base font size to 18–19px, ensure all buttons have generous touch targets (minimum 48×48px), and consider adding a “How to Use” section with clear, step-by-step guidance—this demographic responds well to clarity over assumption.