Website review, no card needed
olliequinn.com website review
Visit site (opens in a new tab)Reviewed 19 November 202631 issues · 81 checks
This review found 31 issues worth fixing on olliequinn.com, 6 of them high impact, across 81 checks. The most urgent: page weight: 11.1 MB in 468 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
83B- #28,004 of 123,109 reviewed websitesbeats 72%
- #18,375 of 69,422 online storesbeats 67%
- #17,800 of 63,201 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.4 s |
| Nov 14, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 102 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 109 ms |
| Jul 4, 2026 | 110 ms |
| Jul 11, 2026 | 116 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 123 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 114 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 100 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 101 ms |
| Oct 10, 2026 | 103 ms |
| Oct 17, 2026 | 103 ms |
| Oct 24, 2026 | 102 ms |
| Oct 31, 2026 | 103 ms |
| Nov 7, 2026 | 104 ms |
| Nov 14, 2026 | 103 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
1.4 s
2.7 s
4.1 s
5.5 s
6.8 s
8.2 s
9.5 s
10.9 s
Speed
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
450 ms · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, groovehq.com and Klaviyo and others), adding 8.6 MB and 1.0 s of main-thread time.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
450 ms · 333 KiB10 images could be 333 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
auglio.com adds 29 ms
29 msauglio.com costs a phone 29 ms of main-thread work and 6.2 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.
Shopify adds 408 ms
408 msShopify costs a phone 408 ms of main-thread work and 1.1 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.
Reduce unused CSS
300 ms · 59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
groovehq.com adds 202 ms
202 msgroovehq.com costs a phone 202 ms of main-thread work and 942 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.
1,977 HTML elements
The page has 1,977 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 129 KiB14 files are served with short cache lifetimes, so returning visitors download them again (129 KiB).
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 177 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need.
Minify JavaScript
28 KiB28 KiB could be saved by minifying JavaScript.
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: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 27.2 s
27.2 sThe page becomes fully interactive after 27.2 s. Good is under 3.8 s.
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 478 ms
478 msScripts block taps and scrolling for 478 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 102 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 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: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 733 ms
733 msReal visitors wait 733 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
Images and page weight
Page weight: 11.1 MB in 468 requests
11.1 MBYour homepage downloads 11.1 MB in 468 requests on a phone: other files 7.6 MB (230), scripts 2.4 MB (161) and images 690 KiB (36). Under 2 MB keeps phones on slow connections fast.
About 3.1 g of CO₂ per visit
3.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.13 g of CO₂e: 376.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 172 images in the HTML carry an alt attribute.
15 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 16 WCAG 2.2 A/AA and best-practice rules on the phone render: 15 passed and 1 failed. 2 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 (“Ollie Quinn Canada” and “”). One clear main headline is easier for people and search engines.
Meta description is long (208 characters)
Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
130 internal links, 5 external
The homepage links to 130 pages on olliequinn.com and 5 external pages.
6 checks passed
Title: 58 characters
Your title is a healthy 58 characters: “Ollie Quinn | Eyeglasses and Sunglasses Online | Eye Exams”.
Canonical URL set
The canonical URL is https://olliequinn.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://olliequinn.com/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
llms.txt published
The site publishes https://olliequinn.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://olliequinn.com/collections/eyeglasses-collection and https://olliequinn.com/collections/eyeglasses-collection/material_acetate all use the title “Ollie Quinn | Free Shipping | Shop Prescription Eyewear Online”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://olliequinn.com/collections/round-optical-frame-collection has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://olliequinn.com/collections/eyeglasses-collection and https://olliequinn.com/collections/eyeglasses-collection/material_acetate use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 5 pages that loaded have a <title>.
Best practices
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 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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.
Only about 23 words
The homepage has only about 23 words of visible text; thin pages give Google and first-time buyers little to go on.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
14 calls to action
The homepage has 14 calls to action, for example “Shop By Material”, “Shop By Style” and “Contact Lenses”.
7 short forms
7 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 2 of them by other companies (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.
47 other companies contacted
Loading the homepage contacts 47 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 olliequinn.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Instafeed · Advance Reorder Repeat Order · Klaviyo Email Marketing Sms · Reorder Master · Judge Me Reviews · Region Restrictions · Simple Reorder · Avada Cookie Bar · Back In Stock · Easify Product Options · hulkapps.com · trackedlink.net · cloudfront.net
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
- Hosting
- Shopify
Company
- Headquarters
- Seattle
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on olliequinn.com, including 15 speed issues, 4 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.