Website review, no card needed
antlerrings.com website review
Visit site (opens in a new tab)Reviewed 20 November 202656 issues · 94 checks
This review found 56 issues worth fixing on antlerrings.com, 18 of them high impact, across 94 checks. The most urgent: page weight: 34.3 MB in 554 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
68D- #105,399 of 119,977 reviewed websitesbeats 10%
- #63,395 of 68,000 online storesbeats 5%
- #58,441 of 61,976 Shopify storesbeats 5%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 133 ms |
| Jun 6, 2026 | 135 ms |
| Jun 13, 2026 | 136 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 160 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 159 ms |
| Sep 12, 2026 | 160 ms |
| Sep 19, 2026 | 158 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 159 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 170 ms |
| Oct 31, 2026 | 172 ms |
| Nov 7, 2026 | 177 ms |
| Nov 14, 2026 | 179 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
3.8 s
7.6 s
11.3 s
15.1 s
18.9 s
22.7 s
26.5 s
30.2 s
Speed
Main-thread work: 19.0 s
A phone's processor spends 19.0 s on main-thread work while loading, 7.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
1.0 s · 448 KiB35 files are served with short cache lifetimes, so returning visitors download them again (448 KiB).
Render-blocking requests
1.4 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8,492 HTML elements
The page has 8,492 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
3.4 MB30 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, govx.com and rebuyengine.com and others), adding 2.9 MB and 2.2 s of main-thread time.
Reduce unused JavaScript
450 ms · 1.6 MBAbout 1.6 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.
Reduce unused CSS
900 ms · 194 KiBAbout 194 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Duplicated JavaScript
757 KiB757 KiB JavaScript is shipped twice across bundles.
Shopify adds 506 ms
506 msShopify costs a phone 506 ms of main-thread work and 842 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 506 ms. During a long task the page ignores taps.
govx.com adds 428 ms
428 msgovx.com costs a phone 428 ms of main-thread work and 7 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.
rebuyengine.com adds 324 ms
324 msrebuyengine.com costs a phone 324 ms of main-thread work and 925 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.
Legacy JavaScript
300 ms · 101 KiBPolyfills for old browsers add 101 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Clarity adds 323 ms
323 msClarity costs a phone 323 ms of main-thread work and 29 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.
okendo.io adds 243 ms
243 msokendo.io costs a phone 243 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Minify JavaScript
6 KiB6 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: 55 ms
55 msYour server sent the HTML in 55 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 32.9 s
32.9 sYour largest element takes 32.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 45.1 s
45.1 sVisually, the page fills in at 45.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 112.9 s
112.9 sThe page becomes fully interactive after 112.9 s. Good is under 3.8 s.
Total Blocking Time: 2.5 s
2.5 sScripts block taps and scrolling for 2.5 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 226 ms
226 msReal visitors wait 226 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 133 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 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.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 34.3 MB in 554 requests
34.3 MBYour homepage downloads 34.3 MB in 554 requests on a phone: images 28.8 MB (55), scripts 2.9 MB (155) and other files 1.6 MB (279). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 17.0 MB together. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
Mobile_Homepage_Header_New_Arrivals_September_2026_abe6acb5- 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).
1 image below the first screen load straight away
1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 9.7 g of CO₂ per visit
9.73 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.73 g of CO₂e: 1167.2 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
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
97 text elements with low contrast
97 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (4 elements)
ARIA dialog and alertdialog nodes should have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 4 mores 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 (88 characters)
Your title is 88 characters, so Google will cut it off around 60: “Antler Rings | Antler Wedding Bands | FREE Shipping from TX since 2015 – AntlerRings.com”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (316 characters)
Your meta description is 316 characters; Google truncates after about 160, so the end of your pitch is cut.
654 internal links, 6 external
The homepage links to 654 pages on antlerrings.com and 6 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://antlerrings.com/.
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://antlerrings.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,699 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://antlerrings.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 linked pages are broken
Your homepage links to https://antlerrings.com/customer_authentication/redirect, https://antlerrings.com/collections/sale and https://antlerrings.com/collections/accessories, which answer with an error. Visitors hit a dead end and search engines drop them.
1 linked page hidden from search
https://antlerrings.com/collections/luxury-loose-diamond-collection is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://antlerrings.com/pages/diamond-information has no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://antlerrings.com/collections/gifts-under-50, https://antlerrings.com/collections/gifts-under-50-copy and https://antlerrings.com/collections/gifts-from-50-100-copy use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://antlerrings.com/collections/best-sellers, https://antlerrings.com/collections/last-call, https://antlerrings.com/collections/gifts-under-50, https://antlerrings.com/collections/gifts-under-50-copy, https://antlerrings.com/collections/gifts-from-50-100-copy and https://antlerrings.com/collections/gift-bundles and 6 others 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 71 found) and read each the way a search engine does.
3 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.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
56 of 65 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 19-field form
Your longest form asks for 19 fields (0 required). Every extra field lowers completion.
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.
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 2,193 words of copy
The homepage carries about 2,193 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
59 calls to action
The homepage has 59 calls to action, for example “Shop”, “Last Call” and “Made to Order”.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks, a star rating and 12 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.
38 cookies set on arrival
38Opening the homepage sets 38 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.
65 other companies contacted
Loading the homepage contacts 65 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 antlerrings.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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Navidium Returns Exchanges · Instafeed · Okendo · Klaviyo Email Marketing Sms · Min Max Limits By Limitsify · Rebuy Personalization Engine · Flair · Triplewhale · Event Promotion Bar · Applovin Shop Integration · Hextom Sales Boost · b-cdn.net · snapchat.com · gotolstoy.com · govx.com · shareasale.com · gorgias.chat · goaffpro.com · 9gtb.com · 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
Stack
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Austin
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 56 issues on antlerrings.com, including 29 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.