Website review, no card needed
designeroptics.com website review
Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 94 checks
This review found 39 issues worth fixing on designeroptics.com, 11 of them high impact, across 94 checks. The most urgent: 5,886 HTML elements. 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
84B- #19,827 of 109,129 reviewed websitesbeats 77%
- #12,889 of 61,805 online storesbeats 73%
- #12,519 of 56,383 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 129 ms |
| May 23, 2026 | 127 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 125 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 123 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 125 ms |
| Aug 8, 2026 | 127 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 126 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 124 ms |
| Sep 12, 2026 | 124 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 121 ms |
| Oct 24, 2026 | 117 ms |
| Oct 31, 2026 | 113 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
0.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.4 s
5.2 s
5.9 s
Speed
5,886 HTML elements
The page has 5,886 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 5.7 s
A phone's processor spends 5.7 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 67
67/100Your mobile performance score is 67. 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 (Google Tag Manager, Google CDN and Shopify and others), adding 1.4 MB and 734 ms of main-thread time.
Render-blocking requests
550 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Reduce unused JavaScript
413 KiBAbout 413 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 354 ms
354 msGoogle Tag Manager costs a phone 354 ms of main-thread work and 371 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
363 KiB12 images could be 363 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google CDN adds 198 ms
198 msGoogle CDN costs a phone 198 ms of main-thread work and 332 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 106 ms
106 msShopify costs a phone 106 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 243 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
50 ms · 160 KiB15 files are served with short cache lifetimes, so returning visitors download them again (160 KiB).
Reduce unused CSS
150 ms · 17 KiBAbout 17 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
50 KiB50 KiB could be saved by minifying JavaScript.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
1 checks passed
Server response: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 16.0 s
16.0 sThe page becomes fully interactive after 16.0 s. Good is under 3.8 s.
Total Blocking Time: 732 ms
732 msScripts block taps and scrolling for 732 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
10 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: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 114 ms
114 msReal visitors wait 114 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.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: 711 ms
711 msReal visitors wait 711 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 129 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.8 MB in 327 requests
3.8 MBYour homepage downloads 3.8 MB in 327 requests on a phone: scripts 1.4 MB (82), other files 1.1 MB (154) and images 1.0 MB (69). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (632 KiB) 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.
5 images far larger than shown
397 KiB5 images are downloaded at several times the size a phone draws them, for example Ray-Ban-Sunglasses-at-Designer-Optics-26-RB3929__39x39_11998 at 1,105 px wide, shown at 171 px. Resized copies would save about 397 KiB.
About 1.1 g of CO₂ per visit
1.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 129.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Unlabelled dropdowns
2 dropdowns have no label.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
9 elements hidden from screen readers can still receive keyboard focus.
38 images without alt text
38 images have no alt text, which hurts accessibility and image search.
156 form fields without a label
156 form fields have no label, so screen readers announce an empty box and autofill guesses.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings skip levels
Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
48 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: 48 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Designeroptics.com Online Shopping for Designer Sunglasses, Eyeglasses”.
Meta description is long (315 characters)
Your meta description is 315 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
604 internal links, 26 external
The homepage links to 604 pages on designeroptics.com and 26 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://designeroptics.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://designeroptics.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: 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 (2,037 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://designeroptics.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://designeroptics.com/pages/wishlist has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://designeroptics.com/blogs/news, https://designeroptics.com/pages/promo-page and https://designeroptics.com/collections/ray-ban 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 143 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5151389&tm=gtm002&Ver=2&mid=347a7891-b790-4aac-ae27-6e58b052965b&bo=1&sid=b5025f40d8fd11f19a0197135b348d1c&vid=b50274d0d8fd11f1a65dbb21acce5813&vids=1&msclkid=N>m_ta.
12 small tap targets
12 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-app.sealsubscriptions.com/shopify/public/css/style.css?shop=designeroptics-com…”.
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 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 744 words of copy
The homepage carries about 744 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: “Contact Lenses” and “Try the chat - you will be surprised ✕”.
26 calls to action
The homepage has 26 calls to action, for example “Order Status”, “Shop All Sunglasses” and “Shop All Eyeglasses”.
82 short forms
82 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 trust badges and “over 15 brands”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 7 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads (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
17Opening 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.
31 other companies contacted
Loading the homepage contacts 31 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 designeroptics.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Designeroptics Chat · Hulk Form Builder · Klaviyo Email Marketing Sms · Judge Me Reviews · Gdpr Cookie Consent · Designer Optics Search · w3apps.co · sealsubscriptions.com · zdops.net · kount.com
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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
Company
- Headquarters
- New York
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on designeroptics.com, including 15 speed issues, 4 SEO 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.