Website review, no card needed

neveneyewear.com logo

neveneyewear.com website review

Visit site (opens in a new tab)Reviewed 4 November 202630 issues · 86 checks

This review found 30 issues worth fixing on neveneyewear.com, 8 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.2 sMay 16Oct 312.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20262.9 s
Oct 31, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
205 ms128 msMay 16Oct 31196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026137 ms
May 23, 2026137 ms
May 30, 2026137 ms
Jun 13, 2026137 ms
Jun 20, 2026138 ms
Jun 27, 2026138 ms
Jul 4, 2026138 ms
Jul 11, 2026137 ms
Jul 18, 2026137 ms
Jul 25, 2026137 ms
Aug 1, 2026137 ms
Aug 8, 2026145 ms
Aug 15, 2026152 ms
Aug 22, 2026155 ms
Aug 29, 2026158 ms
Sep 5, 2026154 ms
Sep 12, 2026152 ms
Sep 19, 2026153 ms
Sep 26, 2026155 ms
Oct 3, 2026163 ms
Oct 10, 2026178 ms
Oct 17, 2026188 ms
Oct 24, 2026195 ms
Oct 31, 2026196 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

Full-page screenshot of neveneyewear.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. neveneyewear.com at 0.6 s0.6 s
  2. neveneyewear.com at 1.2 s1.2 s
  3. neveneyewear.com at 1.8 s1.8 s
  4. neveneyewear.com at 2.4 s2.4 s
  5. neveneyewear.com at 2.9 s2.9 s
  6. neveneyewear.com at 3.5 s3.5 s
  7. neveneyewear.com at 4.1 s4.1 s
  8. neveneyewear.com at 4.7 s4.7 s

Speed

6 to fix68
  • Render-blocking requests

    2.0 s

    19 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.

  • 3,405 HTML elements

    The page has 3,405 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    650 ms · 113 KiB

    2 images could be 113 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 83 KiB

    About 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Google Tag Manager adds 296 ms

    296 ms

    Google Tag Manager costs a phone 296 ms of main-thread work and 443 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and Google CDN and others), adding 566 KiB and 296 ms of main-thread time.

  • Reduce unused JavaScript

    245 KiB

    About 245 KiB of JavaScript is downloaded but never used on this page.

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 186 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    150 ms · 32 KiB

    8 files are served with short cache lifetimes, so returning visitors download them again (32 KiB).

  • 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

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 318 ms of it running JavaScript. That is comfortably low.

  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix100
  • 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: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Shop Lowrider Polarized Sunglasses | Tombstone”.

  • Time to Interactive: 9.6 s

    9.6 s

    The page becomes fully interactive after 9.6 s. Good is under 3.8 s.

  • Tap response (INP) got 43% slower for real visitors

    +43%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 137 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 24% slower for real visitors

    +24%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 2.5 s

    2.5 s

    The first text or image appears after 2.5 s on a phone. Good is under 1.8 s.

  • Speed Index: 3.7 s

    3.7 s

    Visually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

6 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 638 ms

    638 ms

    Real visitors wait 638 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 196 ms

    196 ms

    Scripts block the page for only 196 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.014

    0.014

    The layout barely moves while loading (CLS 0.014, good is under 0.1).

Images and page weight

2 to fix86
  • An image on the first screen is lazy-loaded

    020_mobile.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    40 KiB

    1 image is downloaded at several times the size a phone draws it, for example HP_WM_mobile_02_01.jpg at 748 px wide, shown at 195 px. Resized copies would save about 40 KiB.

  • 1 image in older formats

    1 image (71 KiB) is 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.

  • About 0.5 g of CO₂ per visit

    0.51 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Page weight: 1.8 MB in 125 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 125 requests on a phone: scripts 862 KiB (35), images 479 KiB (65) and fonts 219 KiB (7). That is a lean page.

Accessibility

5 to fixGoogle 9293
  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • 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.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 7 form fields without a label

    7 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 299 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 522 internal links, 32 external

    The homepage links to 522 pages on neveneyewear.com and 32 external pages.

8 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Neven Eyewear: High-quality, affordable polarized sunglasses & custom prescription eyewear. Lost, stolen or broken repl…”.

  • One H1 headline

    Your main headline reads: “Neven Eyewear® | Polarized, On-Trend, Affordable Sunglasses”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Neven Eyewear® | Polarized, On-Trend, Affordable Sunglasses”.

  • Canonical URL set

    The canonical URL is https://neveneyewear.com/.

  • Structured data in place

    Structured data found: 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://neveneyewear.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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 (3,336 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://neveneyewear.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://neveneyewear.com/collections/eyeglasses, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a meta description

    https://neveneyewear.com/collections/safety-eyewear-z87 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://neveneyewear.com/collections/shop-all, https://neveneyewear.com/collections/all-prescription and https://neveneyewear.com/collections/safety-eyewear-z87 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://neveneyewear.com/collections/shop-all and https://neveneyewear.com/collections/all-prescription took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 181 found) and read each the way a search engine does.

4 checks passed
  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 14 small tap targets

    14 of 65 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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,098 words of copy

    The homepage carries about 1,098 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP BEST SELLERS” and “Download App”.

  • 46 calls to action

    The homepage has 46 calls to action, for example “Shop all”, “Shop All” and “Shop Best Sellers”.

  • 4 short forms

    4 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 155 testimonial or review blocks, a star rating and “26,000+ reviews”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 neveneyewear.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Melbourne

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on neveneyewear.com, including 15 speed issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25