Website review, no card needed

fuselenses.com logo

fuselenses.com website review

Visit site (opens in a new tab)Reviewed 5 November 202646 issues · 93 checks

This review found 46 issues worth fixing on fuselenses.com, 16 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. 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
2.2 s1.8 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
158 ms123 msMay 16Oct 31153 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026127 ms
May 23, 2026129 ms
May 30, 2026129 ms
Jun 6, 2026131 ms
Jun 13, 2026130 ms
Jun 20, 2026129 ms
Jun 27, 2026129 ms
Jul 4, 2026129 ms
Jul 11, 2026129 ms
Jul 18, 2026129 ms
Jul 25, 2026129 ms
Aug 1, 2026128 ms
Aug 8, 2026128 ms
Aug 15, 2026129 ms
Aug 22, 2026136 ms
Aug 29, 2026139 ms
Sep 5, 2026146 ms
Sep 12, 2026149 ms
Sep 19, 2026151 ms
Sep 26, 2026153 ms
Oct 3, 2026150 ms
Oct 10, 2026152 ms
Oct 17, 2026154 ms
Oct 24, 2026154 ms
Oct 31, 2026153 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 fuselenses.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fuselenses.com at 1.6 s1.6 s
  2. fuselenses.com at 3.2 s3.2 s
  3. fuselenses.com at 4.8 s4.8 s
  4. fuselenses.com at 6.4 s6.4 s
  5. fuselenses.com at 8.0 s8.0 s
  6. fuselenses.com at 9.6 s9.6 s
  7. fuselenses.com at 11.2 s11.2 s
  8. fuselenses.com at 12.8 s12.8 s

Speed

16 to fix31
  • Reduce unused JavaScript

    4.7 s · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

  • Main-thread work: 18.7 s

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 4,211 HTML elements

    The page has 4,211 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 (Google Tag Manager, alia-prod.com and Dailykarma and others), adding 9.7 MB and 2.7 s of main-thread time.

  • Use efficient cache lifetimes

    700 ms · 557 KiB

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

  • Google Tag Manager adds 635 ms

    635 ms

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

  • alia-prod.com adds 518 ms

    518 ms

    alia-prod.com costs a phone 518 ms of main-thread work and 857 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.

  • Improve image delivery

    567 KiB

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

  • Reduce unused CSS

    450 ms · 89 KiB

    About 89 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.

  • Legacy JavaScript

    400 ms · 93 KiB

    Polyfills for old browsers add 93 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Klaviyo adds 358 ms

    358 ms

    Klaviyo costs a phone 358 ms of main-thread work and 621 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.

  • Dailykarma adds 370 ms

    370 ms

    Dailykarma costs a phone 370 ms of main-thread work and 92 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.

  • cloudfront.net adds 302 ms

    302 ms

    cloudfront.net costs a phone 302 ms of main-thread work and 617 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.

  • Minify JavaScript

    150 ms · 17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Minify CSS

    40 ms · 11 KiB

    11 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

1 checks passed
  • Server response: 65 ms

    65 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 26.0 s

    26.0 s

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

  • Speed Index: 21.3 s

    21.3 s

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

  • Time to Interactive: 45.7 s

    45.7 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

    Scripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 3.6 s

    3.6 s

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

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

    +20%

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

  • 10 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • 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: 163 ms

    163 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 677 ms

    677 ms

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

2 to fix60
  • Page weight: 13.3 MB in 531 requests

    13.3 MB

    Your homepage downloads 13.3 MB in 531 requests on a phone: media 5.0 MB (1), scripts 3.7 MB (252) and images 1.9 MB (36). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    47 KiB

    1 image is downloaded at several times the size a phone draws it, for example bd-change-lens-on-clear.png at 1,498 px wide, shown at 390 px. Resized copies would save about 47 KiB.

  • About 3.8 g of CO₂ per visit

    3.78 g

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

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 8792
  • 4 text elements with low contrast

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

  • 4 tap targets too small

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

  • 1 image without alt text

    1 image has 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 8588
  • 2 H1 headlines

    There are 2 <h1> headlines (“BLACK” and “Save your favorite sunglasses.”). One clear main headline is easier for people and search engines.

  • Meta description is long (240 characters)

    Your meta description is 240 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 2 links crawlers can't follow

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

  • 145 internal links, 3 external

    The homepage links to 145 pages on fuselenses.com and 3 external pages.

6 checks passed
  • Title: 57 characters

    Your title is a healthy 57 characters: “Fuse Replacement Lenses for your Sunglasses – Fuse Lenses”.

  • Canonical URL set

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

  • Structured data in place

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

AI search readiness

2 to fix75
  • Some text only appears after JavaScript runs

    59%

    The HTML your server sends has 648 of the 1,096 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://fuselenses.com/pages/fuse-sales, https://fuselenses.com/pages/fuse-gift-guide, https://fuselenses.com/pages/warranty-returns and https://fuselenses.com/pages/about-amp-color-enhancing have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://fuselenses.com/pages/fuse-sales, https://fuselenses.com/pages/fuse-gift-guide, https://fuselenses.com/pages/warranty-returns, https://fuselenses.com/pages/about-amp-color-enhancing, https://fuselenses.com/collections/oakley and https://fuselenses.com/products/oakley-fuel-cell and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://fuselenses.com/pages/fuse-sales, https://fuselenses.com/pages/fuse-gift-guide, https://fuselenses.com/pages/warranty-returns, https://fuselenses.com/pages/about-amp-color-enhancing, https://fuselenses.com/products/oakley-fuel-cell and https://fuselenses.com/products/ray-ban-rb4187-54mm and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://fuselenses.com/collections/oakley took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • 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 12 pages that loaded have a <title>.

Best practices

5 to fixGoogle 6969
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5140207&tm=gtm002&Ver=2&mid=ca7fddfe-e8d4-4dce-8fe9-5e453f5072a5&bo=1&sid=2a203af0d95611f19246cfff65db85e3&vid=2a204b80d95611f19ed16f6d2db61cab&vids=1&msclkid=N&pi=918.

  • 19 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 2 distorted images

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

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

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.

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

  • About 1,096 words of copy

    The homepage carries about 1,096 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: “Get him the Perfect Gift Shop Now” and “60-Day Guarantee Learn More”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Get him the Perfect Gift Shop Now”, “60-Day Guarantee Learn More” and “What is AMP ? Learn More”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • 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
  • 11 trackers load before any consent

    11

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

  • 40 cookies set on arrival

    40

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

  • 58 other companies contacted

    Loading the homepage contacts 58 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 fuselenses.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 46 issues on fuselenses.com, including 23 speed issues, 3 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