Website review, no card needed
neostrata.com website review
Visit site (opens in a new tab)Reviewed 18 October 202640 issues · 88 checks
This review found 40 issues worth fixing on neostrata.com, 14 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
Site score
70C- #98,257 of 117,566 reviewed websitesbeats 14%
- #60,173 of 66,921 online storesbeats 8%
- #55,782 of 61,017 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.0 s |
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 193 ms |
| May 2, 2026 | 193 ms |
| May 9, 2026 | 195 ms |
| May 16, 2026 | 203 ms |
| May 23, 2026 | 209 ms |
| May 30, 2026 | 207 ms |
| Jun 6, 2026 | 209 ms |
| Jun 13, 2026 | 207 ms |
| Jun 20, 2026 | 205 ms |
| Jun 27, 2026 | 210 ms |
| Jul 4, 2026 | 200 ms |
| Jul 11, 2026 | 209 ms |
| Jul 18, 2026 | 209 ms |
| Jul 25, 2026 | 205 ms |
| Aug 1, 2026 | 226 ms |
| Aug 8, 2026 | 215 ms |
| Aug 15, 2026 | 221 ms |
| Aug 22, 2026 | 219 ms |
| Aug 29, 2026 | 197 ms |
| Sep 5, 2026 | 198 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 181 ms |
| Sep 26, 2026 | 181 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 190 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.0 s
2.0 s
3.0 s
4.0 s
5.0 s
6.0 s
7.0 s
7.9 s
Speed
Render-blocking requests
1.8 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 76). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,952 HTML elements
The page has 3,952 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
750 ms · 544 KiB27 files are served with short cache lifetimes, so returning visitors download them again (544 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Yieldify, Curalate and Optanon and others), adding 1.6 MB and 1.1 s of main-thread time.
Reduce unused JavaScript
563 KiBAbout 563 KiB of JavaScript is downloaded but never used on this page.
Yieldify adds 258 ms
258 msYieldify costs a phone 258 ms of main-thread work and 195 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 124 ms
124 msShopify costs a phone 124 ms of main-thread work and 569 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 240 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Improve image delivery
82 KiB4 images could be 82 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
17 KiB17 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
13 KiB13 KiB JavaScript is shipped twice across bundles.
Phones get a much slower page than desktops
Desktop scores 76 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Time to Interactive: 20.3 s
20.3 sThe page becomes fully interactive after 20.3 s. Good is under 3.8 s.
Largest Contentful Paint: 5.8 s
5.8 sYour largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user INP: 244 ms
244 msReal visitors wait 244 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.15
0.15For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.
Total Blocking Time: 572 ms
572 msScripts block taps and scrolling for 572 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.192
0.192The layout shifts by 0.192 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 193 ms to 190 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 546 ms
546 msReal visitors wait 546 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 16.6 MB in 447 requests
16.6 MBYour homepage downloads 16.6 MB in 447 requests on a phone: media 12.4 MB (1), scripts 1.4 MB (103) and other files 1.2 MB (195). Under 2 MB keeps phones on slow connections fast.
About 4.7 g of CO₂ per visit
4.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.70 g of CO₂e: 564.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Dermatologist-Grade Antiaging Skincare for All Skin Types - NEOSTRATA®”.
2 H1 headlines
There are 2 <h1> headlines (“” and “FROM THE BRAND THAT DISCOVERED GLYCOLIC ACID”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
185 internal links, 19 external
The homepage links to 185 pages on neostrata.com and 19 external pages.
5 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Explore NEOSTRATA products formulated to correct multiple types of skin discoloration, including dark spots, post-acne …”.
Canonical URL set
The canonical URL is https://www.neostrata.com/.
Structured data in place
Structured data found: OnlineStore, WebPage and WebSite.
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://www.neostrata.com/sitemap.xml.
AI search readiness
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
4 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,253 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.neostrata.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.neostrata.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.neostrata.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.neostrata.com/collections/shop-all-skincare, https://www.neostrata.com/pages/offers and https://www.neostrata.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://www.neostrata.com/collections/shop-all-skincare, https://www.neostrata.com/pages/offers, https://www.neostrata.com/customer_authentication/redirect, https://www.neostrata.com/collections/fine-lines-wrinkles, https://www.neostrata.com/collections/lifting-firming and https://www.neostrata.com/collections/dark-spots and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.
3 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.
Best practices
10 small tap targets
10 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 9 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 587 words of copy
The homepage carries about 587 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SIGN UP FOR EMAILS FOR 20% OFF” and “SUBSCRIBE & SAVE FOR 15% OFF”.
39 calls to action
The homepage has 39 calls to action, for example “Shop Our Bestsellers”, “Sign Up for Emails for 20% Off” and “Subscribe & Save for 15% Off”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
27 other companies contacted
Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 neostrata.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on neostrata.com, including 18 speed issues, 4 SEO issues and 5 conversion gaps. 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.