Website review, no card needed
luciaseamoss.com website review
Visit site (opens in a new tab)Reviewed 16 November 202635 issues · 80 checks
This review found 35 issues worth fixing on luciaseamoss.com, 11 of them high impact, across 80 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.9 s · 435 KiB6 images could be 435 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Reduce unused JavaScript
1.7 s · 351 KiBAbout 351 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Render-blocking requests
2.0 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Use efficient cache lifetimes
900 ms · 218 KiB17 files are served with short cache lifetimes, so returning visitors download them again (218 KiB).
Reduce unused CSS
900 ms · 215 KiBAbout 215 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, alia-prod.com and Shopify and others), adding 1.6 MB and 534 ms of main-thread time.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,531 HTML elements
The page has 2,531 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 145 ms
145 msKlaviyo costs a phone 145 ms of main-thread work and 516 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Shopify adds 104 ms
104 msShopify costs a phone 104 ms of main-thread work and 615 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Legacy JavaScript
150 ms · 29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 83 ms. During a long task the page ignores taps.
Minify CSS
22 KiB22 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 18.7 s
18.7 sYour largest element takes 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Organics Nature Mango Pineapple Sea Moss Gel with mango, pi…”.
Time to Interactive: 18.8 s
18.8 sThe page becomes fully interactive after 18.8 s. Good is under 3.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 33 ms
33 msScripts block the page for only 33 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.8 MB in 345 requests
3.8 MBYour homepage downloads 3.8 MB in 345 requests on a phone: scripts 1.5 MB (191), images 1.0 MB (27) and other files 783 KiB (103). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (96 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 130.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
Hidden but focusable
9 elements hidden from screen readers can still receive keyboard focus.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (8 elements)
Headings should not be empty: 8 elements on the page fail this check, rated minor by axe-core.
Table header text should not be empty (2 elements)
Table header text should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
<td> elements in a large <table> do not have table headers.
<td> elements in a large <table> do not have table headers. (1 element).
1 checks passed
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Canonical points to another host
Your canonical URL points to organicsnature.co, not luciaseamoss.com, so Google may credit that host instead.
2 H1 headlines
There are 2 <h1> headlines (“Organics Nature” and “20% OffSitewide”). One clear main headline is easier for people and search engines.
Meta description is long (241 characters)
Your meta description is 241 characters; Google truncates after about 160, so the end of your pitch is cut.
111 internal links, 6 external
The homepage links to 111 pages on luciaseamoss.com and 6 external pages.
5 checks passed
Title: 53 characters
Your title is a healthy 53 characters: “Shop Wild Sea Moss | Black Seed Oil | Organics Nature”.
Structured data in place
Structured data found: Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://luciaseamoss.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (2,491 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://luciaseamoss.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://luciaseamoss.com/pages/ocean-cleanup-initiative has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56308149&Ver=2&mid=e665ec7b-1474-4884-bd77-7abd4232301a&bo=1&sid=0d5ceee0e21311f1a453ebaab8f06613&vid=0d5d0460e21311f1bfcc7f48b5df9db1&vids=1&msclkid=N&pi=918639831&lg.
3 small tap targets
3 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 918 words of copy
The homepage carries about 918 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop the Sale”.
14 calls to action
The homepage has 14 calls to action, for example “🌿 NEW SEA MOSS GEL - SHOP NOW”, “Shop All” and “Shop Now”.
12 short forms
12 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 67 testimonial or review blocks, a star rating, 1 trust badge and “70,000+ reviews”.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 3 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
31 cookies set on arrival
31Opening the homepage sets 31 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
41 other companies contacted
Loading the homepage contacts 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at luciaseamoss.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Microsoft Clarity · Hulk Contact Form Builder · Postscript Sms Marketing · Uppromote Affiliate · Pagefly Ai Page Builder · Klaviyo Email Marketing Sms · Affliate By Secomapp · Aftersell · Test Sms · Appstle Bundles · Free Gift · loox.io · trafficmanager.net · shareasale.com · cloudfront.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on luciaseamoss.com, including 16 speed issues and 3 SEO issues. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.