Website review, no card needed
getnexgen.com website review
Visit site (opens in a new tab)Reviewed 21 October 202635 issues · 86 checks
This review found 35 issues worth fixing on getnexgen.com, 9 of them high impact, across 86 checks. The most urgent: page weight: 18.9 MB in 376 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
88B- #5,626 of 117,615 reviewed websitesbeats 93%
- #3,103 of 66,923 online storesbeats 93%
- #3,008 of 61,018 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.3 s |
| May 9, 2026 | 5.2 s |
| May 16, 2026 | 5.2 s |
| May 23, 2026 | 5.2 s |
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 5.0 s |
| Jun 20, 2026 | 5.1 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 5.2 s |
| Jul 11, 2026 | 5.3 s |
| Jul 18, 2026 | 5.3 s |
| Jul 25, 2026 | 5.2 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.2 s |
| Aug 15, 2026 | 5.3 s |
| Aug 22, 2026 | 5.2 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 139 ms |
| May 9, 2026 | 139 ms |
| May 16, 2026 | 140 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 150 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 163 ms |
| Jun 20, 2026 | 166 ms |
| Jun 27, 2026 | 173 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 171 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 176 ms |
| Aug 8, 2026 | 187 ms |
| Aug 15, 2026 | 211 ms |
| Aug 22, 2026 | 216 ms |
| Aug 29, 2026 | 221 ms |
| Sep 5, 2026 | 204 ms |
| Sep 12, 2026 | 194 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 197 ms |
| Oct 3, 2026 | 207 ms |
| Oct 10, 2026 | 213 ms |
| Oct 17, 2026 | 209 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
Speed
4,219 HTML elements
The page has 4,219 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Cloudflare CDN and Reviews.io and others), adding 11.5 MB and 330 ms of main-thread time.
Shopify adds 164 ms
164 msShopify costs a phone 164 ms of main-thread work and 11.4 MB 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.
Mobile performance score: 66
66/100Your mobile performance score is 66 (desktop: 85). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Use efficient cache lifetimes
150 ms · 383 KiB12 files are served with short cache lifetimes, so returning visitors download them again (383 KiB).
Reduce unused CSS
410 ms · 34 KiBAbout 34 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 410 ms faster on a phone.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 837 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
150 ms · 13 KiB13 KiB could be saved by minifying JavaScript.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 114 ms. During a long task the page ignores taps.
Improve image delivery
102 KiB2 images could be 102 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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 CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 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.
Largest Contentful Paint: 14.1 s
14.1 sYour largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Professional.”.
Time to Interactive: 19.9 s
19.9 sThe page becomes fully interactive after 19.9 s. Good is under 3.8 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Tap response (INP) got 52% slower for real visitors
+52%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 139 ms to 209 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
7 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 INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 66% faster for real visitors
-66%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.3 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Total Blocking Time: 36 ms
36 msScripts block the page for only 36 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 18.9 MB in 376 requests
18.9 MBYour homepage downloads 18.9 MB in 376 requests on a phone: media 12.8 MB (4), images 3.4 MB (85) and other files 1.7 MB (182). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.
2 images in older formats
2 images (1.4 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
2 images below the first screen load straight away
2 images further down the page (843 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.4 g of CO₂ per visit
5.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.36 g of CO₂e: 642.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
18 images without alt text
18 images have no alt text, which hurts accessibility and image search.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
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.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (20 elements).
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. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “WILL YOU BE OUR NEXT AMAZING REVIEW?”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
184 internal links, 13 external
The homepage links to 184 pages on getnexgen.com and 13 external pages.
7 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Shop the most powerful car detailing supplies ever made. Simple application and professional results. Manufactured in t…”.
Title: 39 characters
Your title is a healthy 39 characters: “Nexgen | Premium Car Detailing Supplies”.
Canonical URL set
The canonical URL is https://getnexgen.com/.
Structured data in place
Structured data found: FAQPage, Organization and WebSite.
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://getnexgen.com/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, description and contact details; logo and sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,579 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://getnexgen.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://getnexgen.com/products/ceramic-clay-bar-detail-kit-offer is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 64 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
103 distorted images
103 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
2 checks passed
Tap targets are thumb-sized
8 of 8 tappable elements near the top are at least 24 px.
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.
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.
About 1,329 words of copy
The homepage carries about 1,329 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
18 calls to action
The homepage has 18 calls to action, for example “SHOP ALL BEST SELLERS...”, “SHOP ALL CERAMICS...” and “SHOP ALL EXTERIOR...”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks and 3 trust badges.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (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.
28 other companies contacted
Loading the homepage contacts 28 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 getnexgen.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on getnexgen.com, including 16 speed issues, 2 SEO issues and 4 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.