Website review, no card needed
randolphusa.com website review
Visit site (opens in a new tab)Reviewed 7 November 202628 issues · 79 checks
This review found 28 issues worth fixing on randolphusa.com, 12 of them high impact, across 79 checks. The most urgent: improve image delivery. 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
85B- #15,423 of 112,742 reviewed websitesbeats 82%
- #9,935 of 64,809 online storesbeats 79%
- #9,664 of 59,248 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 132 ms |
| May 23, 2026 | 137 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 151 ms |
| Aug 1, 2026 | 151 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 157 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 157 ms |
| Sep 5, 2026 | 143 ms |
| Sep 12, 2026 | 136 ms |
| Sep 19, 2026 | 132 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 140 ms |
| Oct 10, 2026 | 150 ms |
| Oct 17, 2026 | 150 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 2026 | 138 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
18.0 s · 3.0 MB33 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 18.0 s faster on a phone.
Reduce unused CSS
1.4 s · 276 KiBAbout 276 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Use efficient cache lifetimes
350 ms · 77 KiB18 files are served with short cache lifetimes, so returning visitors download them again (77 KiB).
Reduce unused JavaScript
150 ms · 267 KiBAbout 267 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Forter, boostcommerce.io and Shopify and others), adding 1.4 MB and 179 ms of main-thread time.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,243 HTML elements
The page has 2,243 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 36 ms
36 msShopify costs a phone 36 ms of main-thread work and 1.0 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.
Minify JavaScript
15 KiB15 KiB could be saved by minifying JavaScript.
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 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: 34 ms
34 msYour server sent the HTML in 34 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 33.8 s
33.8 sYour largest element takes 33.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cole Hauser wearing Randolph aviator sunglasses, leaning ag…”.
Time to Interactive: 40.0 s
40.0 sThe page becomes fully interactive after 40.0 s. Good is under 3.8 s.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 132 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 192 ms
192 msReal visitors wait 192 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 568 ms
568 msReal visitors wait 568 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 9 ms
9 msScripts block the page for only 9 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.9 MB in 408 requests
8.9 MBYour homepage downloads 8.9 MB in 408 requests on a phone: images 5.0 MB (51), other files 1.4 MB (257) and scripts 1.4 MB (60). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.
12 images far larger than shown
1.3 MB12 images are downloaded at several times the size a phone draws them, for example Home_Page_Banner_Mobile__HGG_CH.png at 1,250 px wide, shown at 390 px. Resized copies would save about 1.3 MB.
28 images below the first screen load straight away
28 images further down the page (2.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.52 g of CO₂e: 302.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
191 internal links, 17 external
The homepage links to 191 pages on randolphusa.com and 17 external pages.
8 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Shop Randolph sunglasses, handcrafted in the USA since 1973. Military-grade quality, polarized and prescription options…”.
One H1 headline
Your main headline reads: “GIFTS MADE TO LAST.”.
Title: 50 characters
Your title is a healthy 50 characters: “Randolph USA | American-Made Sunglasses Since 1973”.
Canonical URL set
The canonical URL is https://www.randolphusa.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://www.randolphusa.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,278 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.randolphusa.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.randolphusa.com/collections/womens-sunglasses, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a meta description
https://www.randolphusa.com/pages/sunglasses has no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://www.randolphusa.com/collections/new-arrivals, https://www.randolphusa.com/collections/aviator-best-sellers, https://www.randolphusa.com/collections/mens-sunglasses, https://www.randolphusa.com/collections/the-military-aviator, https://www.randolphusa.com/collections/aviators and https://www.randolphusa.com/collections/teardrop-shaped-sunglasses and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.randolphusa.com/collections/round-shaped-sunglasses has 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.
3 pages slow to respond
https://www.randolphusa.com/collections/polarized-sunglasses, https://www.randolphusa.com/collections/non-polarized-sunglasses and https://www.randolphusa.com/collections/glass-lens-sunglasses took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 81 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 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://jelly.mdhv.io/v1/star.gif?pid=lBDvwweEehJYotz5m3C6ZXBfIjHo&src=mh&evt=hi.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
23 of 26 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 401 words of copy
The homepage carries about 401 words of visible text.
4 checks passed
28 calls to action
The homepage has 28 calls to action, for example “Shop All Styles”, “SHOP ALL PRESCRIPTION” and “Shop All Collections”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager 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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
21 other companies contacted
Loading the homepage contacts 21 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 randolphusa.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Boost Ai Search Filter · Yotpo Product Reviews · Eg Auto Add To Cart · Okendo · Klaviyo Email Marketing Sms · Stape Remix · Lensadvisor · Orbe Geolocation · trafficmanager.net · shopkeepertools.com · global-e.com · govx.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 Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Employees
- 76
- Founded
- 1972
- Headquarters
- Randolph
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on randolphusa.com, including 13 speed issues and 3 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.