Website review, no card needed
ciovita.com website review
Visit site (opens in a new tab)Reviewed 24 October 202625 issues · 79 checks
This review found 25 issues worth fixing on ciovita.com, 13 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- #16,656 of 124,162 reviewed websitesbeats 82%
- #10,478 of 69,798 online storesbeats 80%
- #10,172 of 63,482 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 133 ms |
| May 9, 2026 | 141 ms |
| May 16, 2026 | 145 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 131 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 123 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 122 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 134 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 152 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 155 ms |
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 152 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 150 ms |
| Oct 17, 2026 | 153 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.6 s
1.1 s
1.7 s
2.3 s
2.8 s
3.4 s
4.0 s
4.5 s
Speed
Improve image delivery
1.8 s · 321 KiB17 images could be 321 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
8,219 HTML elements
The page has 8,219 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 62
62/100Your mobile performance score is 62 (desktop: 84). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Klaviyo adds 137 ms
137 msKlaviyo costs a phone 137 ms of main-thread work and 336 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.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and Cloudflare CDN and others), adding 626 KiB and 295 ms of main-thread time.
Reduce unused JavaScript
160 ms · 182 KiBAbout 182 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 160 ms faster on a phone.
Reduce unused CSS
190 ms · 75 KiBAbout 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.
Legacy JavaScript
100 ms · 18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
53 KiB9 files are served with short cache lifetimes, so returning visitors download them again (53 KiB).
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: 107 ms
107 msYour server sent the HTML in 107 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.2 s
13.2 sYour largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and similar technologies to store and access…”.
Time to Interactive: 15.0 s
15.0 sThe page becomes fully interactive after 15.0 s. Good is under 3.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 224 ms
224 msScripts block taps and scrolling for 224 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 133 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 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: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 157 ms
157 msReal visitors wait 157 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.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 764 ms
764 msReal visitors wait 764 ms for your server to start answering (75th percentile). Good is under 800 ms.
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: 12.4 MB in 222 requests
12.4 MBYour homepage downloads 12.4 MB in 222 requests on a phone: media 9.4 MB (2), images 1.0 MB (32) and scripts 835 KiB (78). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (255 KiB) 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.
About 3.5 g of CO₂ per visit
3.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.52 g of CO₂e: 422.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 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
3 text elements with low contrast
3 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 (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail 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. (60 elements).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
268 internal links, 12 external
The homepage links to 268 pages on ciovita.com and 12 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Ciovita design and manufacture precision engineered cycling kit. Get world class bike wear including jerseys, bib short…”.
Title: 59 characters
Your title is a healthy 59 characters: “Cycling Kit | Leaders in Cycle Wear | Ciovita International”.
Canonical URL set
The canonical URL is https://www.ciovita.com/en-us.
Structured data in place
Structured data found: 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.ciovita.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: 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 (2,318 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ciovita.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://www.ciovita.com/en-us/collections/ams-cpt has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.ciovita.com/en-us/collections/ams-cpt, https://www.ciovita.com/en-us/collections/speed-company-racing, https://www.ciovita.com/en-us/collections/the-archive and https://www.ciovita.com/en-us/collections/mens-cycling-apparel 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 99 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
62 of 63 tappable elements near the top are at least 24 px.
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 925 words of copy
The homepage carries about 925 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: “Learn more”.
21 calls to action
The homepage has 21 calls to action, for example “Shop All”, “Shop All Events” and “Contact Us”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
32 other companies contacted
Loading the homepage contacts 32 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 ciovita.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 Hosted
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on ciovita.com, including 11 speed issues, 2 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.