Website review, no card needed
circlesportswear.com website review
Visit site (opens in a new tab)Reviewed 9 November 202635 issues · 85 checks
This review found 35 issues worth fixing on circlesportswear.com, 10 of them high impact, across 85 checks. The most urgent: page weight: 33.2 MB in 412 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
84B- #22,487 of 126,178 reviewed websitesbeats 77%
- #14,337 of 70,384 online storesbeats 74%
- #13,899 of 63,910 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 179 ms |
| May 30, 2026 | 178 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 180 ms |
| Jun 20, 2026 | 188 ms |
| Jun 27, 2026 | 192 ms |
| Jul 4, 2026 | 193 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 197 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 197 ms |
| Aug 8, 2026 | 197 ms |
| Aug 15, 2026 | 198 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 210 ms |
| Sep 5, 2026 | 212 ms |
| Sep 12, 2026 | 209 ms |
| Sep 19, 2026 | 202 ms |
| Sep 26, 2026 | 203 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 204 ms |
| Oct 17, 2026 | 204 ms |
| Oct 24, 2026 | 200 ms |
| Oct 31, 2026 | 196 ms |
| Nov 7, 2026 | 195 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.2 s
1.8 s
2.4 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Avoid multiple page redirects
3.2 sThe page goes through 1 redirect before it starts loading, costing about 3.2 s. Link and advertise the final URL directly.
Improve image delivery
300 ms · 1.3 MB20 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.1 MB and 612 ms of main-thread time.
Reduce unused JavaScript
370 KiBAbout 370 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 309 ms
309 msGoogle Tag Manager costs a phone 309 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.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 871 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 175 ms
175 msShopify costs a phone 175 ms of main-thread work and 435 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.
Minify JavaScript
160 ms · 8 KiB8 KiB could be saved by minifying JavaScript.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.
Legacy JavaScript
59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need.
Reduce unused CSS
57 KiBAbout 57 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
26 KiB22 files are served with short cache lifetimes, so returning visitors download them again (26 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.2 s
21.2 sThe page becomes fully interactive after 21.2 s. Good is under 3.8 s.
Largest Contentful Paint: 6.4 s
6.4 sYour largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
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.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 179 ms to 195 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 189 ms
189 msReal visitors wait 189 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: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 351 ms
351 msReal visitors wait 351 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 118 ms
118 msScripts block the page for only 118 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 33.2 MB in 412 requests
33.2 MBYour homepage downloads 33.2 MB in 412 requests on a phone: media 28.5 MB (4), images 2.0 MB (47) and scripts 1.3 MB (152). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
HP-MOBILE-BUFF_1.png 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 9.4 g of CO₂ per visit
9.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.41 g of CO₂e: 1128.6 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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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.
54 links without text
54 visible links have no text or label, so screen readers cannot say where they go.
16 form fields without a label
16 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 108 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
7 H1 headlines
There are 7 <h1> headlines (“”, “CIRCLE x OCTOBRE ÉDITIONS” and “CIRCLE x BUFF”). One clear main headline is easier for people and search engines.
156 internal links, 8 external
The homepage links to 156 pages on circlesportswear.com and 8 external pages.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Des vêtements et chaussures de running durables, conçus pour allier performance et responsabilité. Courir, innover, s’e…”.
Title: 62 characters
Your title is a healthy 62 characters: “Circle Sportswear - Vêtements & Chaussures de Running Durables”.
Canonical URL set
The canonical URL is https://circlesportswear.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://circlesportswear.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 (796 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://circlesportswear.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages without a meta description
https://circlesportswear.com/pages/contact-us, https://circlesportswear.com/pages/parrainage, https://circlesportswear.com/collections/tshirts-manches-longues-homme, https://circlesportswear.com/collections/hoodies-jogging-homme, https://circlesportswear.com/collections/vestes-homme and https://circlesportswear.com/collections/leggings-running-homme and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://circlesportswear.com/pages/contact-us and https://circlesportswear.com/pages/parrainage 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 66 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 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 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
83 of 94 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 trust badge. 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 417 words of copy
The homepage carries about 417 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “[email protected]”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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.
35 other companies contacted
Loading the homepage contacts 35 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 circlesportswear.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Essential A B Testing · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Kleep Circle Sportswear · Ekookie · Back In Stock · Sticky Cart By Qikify · Booster Kit By Qikify · amazonaws.com · loyoly.io
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
- The footer still says © 2020.
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Paris
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on circlesportswear.com, including 13 speed issues, 2 SEO 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.