Website review, no card needed
fidelitydenim.com website review
Visit site (opens in a new tab)Reviewed 5 November 202631 issues · 81 checks
This review found 31 issues worth fixing on fidelitydenim.com, 6 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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- #21,209 of 117,615 reviewed websitesbeats 77%
- #13,814 of 66,923 online storesbeats 73%
- #13,412 of 61,018 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.0 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 911 ms |
| Jul 18, 2026 | 979 ms |
| Jul 25, 2026 | 981 ms |
| Aug 1, 2026 | 960 ms |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 983 ms |
| Sep 12, 2026 | 949 ms |
| Sep 19, 2026 | 933 ms |
| Sep 26, 2026 | 904 ms |
| Oct 3, 2026 | 899 ms |
| Oct 10, 2026 | 875 ms |
| Oct 17, 2026 | 827 ms |
| Oct 24, 2026 | 775 ms |
| Oct 31, 2026 | 801 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 87 ms |
| May 23, 2026 | 87 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 94 ms |
| Jul 4, 2026 | 88 ms |
| Jul 11, 2026 | 83 ms |
| Jul 18, 2026 | 81 ms |
| Jul 25, 2026 | 82 ms |
| Aug 1, 2026 | 82 ms |
| Aug 8, 2026 | 88 ms |
| Aug 15, 2026 | 89 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 87 ms |
| Sep 12, 2026 | 89 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 84 ms |
| Oct 17, 2026 | 83 ms |
| Oct 24, 2026 | 80 ms |
| Oct 31, 2026 | 84 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.8 s
1.5 s
2.3 s
3.0 s
3.8 s
4.5 s
5.3 s
6.1 s
Speed
Reduce unused JavaScript
2.1 s · 348 KiBAbout 348 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (rebuyengine.com, Klaviyo and POWr and others), adding 1.2 MB and 979 ms of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
450 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
rebuyengine.com adds 344 ms
344 msrebuyengine.com costs a phone 344 ms of main-thread work and 667 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.
Reduce unused CSS
310 ms · 83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Use efficient cache lifetimes
300 ms · 59 KiB11 files are served with short cache lifetimes, so returning visitors download them again (59 KiB).
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 260 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Improve image delivery
116 KiB5 images could be 116 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.9 s
14.9 sYour largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 17.7 s
17.7 sThe page becomes fully interactive after 17.7 s. Good is under 3.8 s.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 418 ms
418 msScripts block taps and scrolling for 418 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 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.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 87 ms to 84 ms 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 108 ms
108 msReal visitors wait 108 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 251 requests
2.8 MBYour homepage downloads 2.8 MB in 251 requests on a phone: scripts 1.2 MB (109), other files 721 KiB (97) and images 484 KiB (23). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
TORINO_PISTON_MOBILE_d630d8bb-d421-4937-8bca-9a7c49d74daa.jp 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 (25 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 95.9 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
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail 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.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h5, h1 → h5 and h1 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“”, “DEVOTED TO CRAFT.” and “DEVOTED TO DENIM.”). One clear main headline is easier for people and search engines.
Meta description is long (217 characters)
Your meta description is 217 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
89 internal links, 4 external
The homepage links to 89 pages on fidelitydenim.com and 4 external pages.
5 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “Fidelity Denim | Official Online Store”.
Canonical URL set
The canonical URL is https://fidelitydenim.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://fidelitydenim.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://fidelitydenim.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (429 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages without a meta description
https://fidelitydenim.com/collections/all-new-arrivals, https://fidelitydenim.com/collections/fidelity-mens-new-arrivals, https://fidelitydenim.com/collections/fidelity-womens-new-arrivals, https://fidelitydenim.com/collections/fidelity-women, https://fidelitydenim.com/collections/fidelity-womens-straight-leg and https://fidelitydenim.com/collections/fidelity-womens-wide-leg and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 66 found) and read each the way a search engine does.
6 checks passed
Linked pages load
7 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.
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 7 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 4 testimonial or review blocks. 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.
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 299 words of copy
The homepage carries about 299 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP MEN” and “SHOP WOMEN”.
9 calls to action
The homepage has 9 calls to action, for example “SHOP BY FIT”, “SHOP BY STYLE” and “SHOP MEN”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
39 other companies contacted
Loading the homepage contacts 39 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 fidelitydenim.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
Parkour Facebook Pixel · Microsoft Clarity · Rebuy Personalization Engine · Swatch King · Variant Image Swatch · azureedge.net · rakutenadvertising.io · b-cdn.net · klaviyo.com · powr.io · rebuyengine.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
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Bryn Athyn
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 fidelitydenim.com, including 15 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.