Website review, no card needed
giordanacycling.com website review
Visit site (opens in a new tab)Reviewed 8 November 202642 issues · 89 checks
This review found 42 issues worth fixing on giordanacycling.com, 15 of them high impact, across 89 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
72C- #96,747 of 125,084 reviewed websitesbeats 19%
- #59,482 of 70,104 online storesbeats 12%
- #55,370 of 63,708 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 178 ms |
| May 23, 2026 | 191 ms |
| May 30, 2026 | 200 ms |
| Jun 6, 2026 | 203 ms |
| Jun 13, 2026 | 212 ms |
| Jun 20, 2026 | 199 ms |
| Jun 27, 2026 | 210 ms |
| Jul 4, 2026 | 213 ms |
| Jul 11, 2026 | 202 ms |
| Jul 18, 2026 | 206 ms |
| Jul 25, 2026 | 187 ms |
| Aug 1, 2026 | 194 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 183 ms |
| Aug 22, 2026 | 186 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 182 ms |
| Sep 19, 2026 | 188 ms |
| Sep 26, 2026 | 196 ms |
| Oct 3, 2026 | 189 ms |
| Oct 10, 2026 | 196 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 194 ms |
| Oct 31, 2026 | 194 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.0 s
Speed
Reduce unused JavaScript
1.5 s · 339 KiBAbout 339 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,456 HTML elements
The page has 3,456 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
600 ms · 2.1 MB15 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Use efficient cache lifetimes
900 ms · 250 KiB22 files are served with short cache lifetimes, so returning visitors download them again (250 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Hotjar, Klaviyo and Clarity and others), adding 3.4 MB and 762 ms of main-thread time.
Render-blocking requests
750 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 49 ms
49 msShopify costs a phone 49 ms of main-thread work and 2.4 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.
Klaviyo adds 106 ms
106 msKlaviyo costs a phone 106 ms of main-thread work and 482 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
280 ms · 189 KiBAbout 189 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
Legacy JavaScript
150 ms · 55 KiBPolyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 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.
Real-user CLS: 0.59
0.59For real visitors the layout shifts by 0.59 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 16.8 s
16.8 sYour largest element takes 16.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 21.8 s
21.8 sThe page becomes fully interactive after 21.8 s. Good is under 3.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.57
0.57The layout shifts by 0.57 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 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 178 ms to 194 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 594 ms
594 msReal visitors wait 594 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 142 ms
142 msScripts block the page for only 142 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.5 MB in 365 requests
9.5 MBYour homepage downloads 9.5 MB in 365 requests on a phone: images 6.3 MB (94), scripts 1.4 MB (100) and other files 1.3 MB (140). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
1.6 MB8 images are downloaded at several times the size a phone draws them, for example giordana-beyond-gravel-bib-men-leopard-side-1.jpg at 2,000 px wide, shown at 343 px. Resized copies would save about 1.6 MB.
1 image over 500 KB
giordana-beyond-gravel-bib-men-leopard-side-1.jpg weighs 821 KiB. On a phone connection a single image that size takes seconds.
9 images in older formats
9 images (2.3 MB) 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.
9 images below the first screen load straight away
9 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
giordana-cycling-fall-winter-26-banner-mobile-1-1.jpg 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).
About 2.7 g of CO₂ per visit
2.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.70 g of CO₂e: 323.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
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.
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.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h1 → h3), which makes the page harder to scan with a screen reader.
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 53 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Premium Cycling Apparel | Italian Cycling Gear | Giordana – Giordana Cycling”.
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//giordanacycling.com/cdn/shop/files/giordana_logo.png?…”.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
460 internal links, 28 external
The homepage links to 460 pages on giordanacycling.com and 28 external pages.
5 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Giordana crafts premium cycling apparel in Italy for pros and everyday riders alike. Upgrade your cycling gear and perf…”.
One H1 headline
Your main headline reads: “GIORDANA PREMIUM ITALIAN CYCLING APPAREL. ENGINEERED FOR PERFORMANCE. DESIGNED FOR WHAT'S NEXT.”.
Canonical URL set
The canonical URL is https://giordanacycling.com/.
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://giordanacycling.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,535 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://giordanacycling.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://giordanacycling.com/collections/fall-winter-season has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://giordanacycling.com/pages/giordana-la-posta, https://giordanacycling.com/collections/beyond-gravel and https://giordanacycling.com/collections/giordana-x-kristopher-brock 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 120 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=52017217&tm=gtm002&Ver=2&mid=4dc509f4-5547-4ea1-9602-197ba9e83aed&bo=1&sid=01f09930db3f11f1b575959423991636&vid=01f0cd90db3f11f18af233c2e8c0a597&vids=1&msclkid=N&pi=91.
28 small tap targets
28 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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 ()”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 770 words of copy
The homepage carries about 770 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: “SUBSCRIBE” and “SHOP NOW”.
21 calls to action
The homepage has 21 calls to action, for example “SHOP ALL”, “LEARN MORE” and “CONTACT US”.
16 short forms
16 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
46 other companies contacted
Loading the homepage contacts 46 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 giordanacycling.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Shopify
Company
- Founded
- 1971
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on giordanacycling.com, including 18 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.