Website review, no card needed

herosunglasses.com logo

herosunglasses.com website review

Visit site (opens in a new tab)Reviewed 16 November 202640 issues · 86 checks

This review found 40 issues worth fixing on herosunglasses.com, 14 of them high impact, across 86 checks. The most urgent: page weight: 5.7 MB in 529 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

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

How it loaded on a phone

  1. herosunglasses.com at 1.2 s1.2 s
  2. herosunglasses.com at 2.4 s2.4 s
  3. herosunglasses.com at 3.6 s3.6 s
  4. herosunglasses.com at 4.8 s4.8 s
  5. herosunglasses.com at 6.0 s6.0 s
  6. herosunglasses.com at 7.2 s7.2 s
  7. herosunglasses.com at 8.4 s8.4 s
  8. herosunglasses.com at 9.6 s9.6 s

Speed

11 to fix64
  • 3,582 HTML elements

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. 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 (chatra.io, Shopify and Google Tag Manager and others), adding 1.6 MB and 789 ms of main-thread time.

  • Reduce unused JavaScript

    642 KiB

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

  • Render-blocking requests

    500 ms

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

  • Main-thread work: 3.2 s

    A phone's processor spends 3.2 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • chatra.io adds 275 ms

    275 ms

    chatra.io costs a phone 275 ms of main-thread work and 327 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.

  • Use efficient cache lifetimes

    302 KiB

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

  • Improve image delivery

    301 KiB

    16 images could be 301 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Shopify adds 220 ms

    220 ms

    Shopify costs a phone 220 ms of main-thread work and 613 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.

  • Google Tag Manager adds 127 ms

    127 ms

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

  • Font display

    200 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

  • 8 long tasks on the main thread

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

  • Reduce unused CSS

    54 KiB

    About 54 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    25 KiB

    Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need.

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

5 to fix65
  • Largest Contentful Paint: 9.2 s

    9.2 s

    Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 23.6 s

    23.6 s

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

  • Speed Index: 7.7 s

    7.7 s

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

  • 28 images without width and height

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 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
  • Total Blocking Time: 141 ms

    141 ms

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

  • Cumulative Layout Shift: 0.06

    0.06

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

Images and page weight

2 to fix64
  • Page weight: 5.7 MB in 529 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 529 requests on a phone: images 2.0 MB (137), scripts 1.6 MB (89) and other files 1.2 MB (248). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Hero_Logo_2Transparent_a286662a-ce62-42ed-aded-f4826f28dc21. 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).

  • About 1.6 g of CO₂ per visit

    1.60 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.60 g of CO₂e: 192.6 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

12 to fixGoogle 6985
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Hidden but focusable

    16 elements hidden from screen readers can still receive keyboard focus.

  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links look like plain text

    4 links inside paragraphs rely on colour alone to stand out.

  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

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

  • 37 images without alt text

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

  • 16 links without text

    16 visible links have no text or label, so screen readers cannot say where they go.

  • 4 form fields without a label

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

1 checks passed
  • 53 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: 53 passed and 11 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8595
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 272 internal links, 11 external

    The homepage links to 272 pages on herosunglasses.com and 11 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Shop authentic designer sunglasses online from top brands. Discover sport, polarized, and luxury styles with special pr…”.

  • One H1 headline

    Your main headline reads: “Shop Designer Sunglasses for Style, Performance & Everyday Wear”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Shop Designer Sunglasses Online | Hero Sunglasses”.

  • Canonical URL set

    The canonical URL is https://www.herosunglasses.com/.

  • Structured data in place

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

AI search readiness

100
  • No llms.txt

    There is no https://www.herosunglasses.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,576 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 3 pages without an H1

    https://www.herosunglasses.com/collections/oakley, https://www.herosunglasses.com/collections/versace and https://www.herosunglasses.com/collections/ralph-lauren 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 92 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    3 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 3 pages that loaded have a meta description.

  • 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

4 to fixGoogle 7383
  • 9 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

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

  • 26 distorted images

    26 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • A 15-field form

    Your longest form asks for 15 fields (15 required). Every extra field lowers completion.

  • About 461 words of copy

    The homepage carries about 461 words of visible text.

  • Urgency cues

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CREATE AN ACCOUNT TO UNLOCK HERO PRICING”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Create an account to unlock hero pricing”, “shop by profession” and “shop by activity”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 3 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

1 to fix
  • 4 trackers load before any consent

    4

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

  • 17 cookies set on arrival

    17

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

  • 23 other companies contacted

    Loading the homepage contacts 23 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 herosunglasses.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Chatra Live Chat Chatbot · Hulk Contact Form Builder · Upcart · Swym Wishlist Plus

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

  • The footer still says © 2024.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
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 herosunglasses.com, including 16 speed issues, 2 SEO issues and 2 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

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