Website review, no card needed
gino-rossi.com website review
Visit site (opens in a new tab)Reviewed 18 November 202647 issues · 88 checks
This review found 47 issues worth fixing on gino-rossi.com, 21 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.7 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 5.0 s |
| Sep 12, 2026 | 4.9 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 5.0 s |
| Oct 3, 2026 | 5.0 s |
| Oct 10, 2026 | 5.0 s |
| Oct 17, 2026 | 5.0 s |
| Oct 24, 2026 | 4.8 s |
| Oct 31, 2026 | 4.6 s |
| Nov 7, 2026 | 4.5 s |
| Nov 14, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 191 ms |
| Jun 6, 2026 | 192 ms |
| Jun 13, 2026 | 189 ms |
| Jun 20, 2026 | 188 ms |
| Jun 27, 2026 | 193 ms |
| Jul 4, 2026 | 204 ms |
| Jul 11, 2026 | 220 ms |
| Jul 18, 2026 | 242 ms |
| Jul 25, 2026 | 256 ms |
| Aug 1, 2026 | 266 ms |
| Aug 8, 2026 | 288 ms |
| Aug 15, 2026 | 317 ms |
| Aug 22, 2026 | 358 ms |
| Aug 29, 2026 | 380 ms |
| Sep 5, 2026 | 384 ms |
| Sep 12, 2026 | 387 ms |
| Sep 19, 2026 | 388 ms |
| Sep 26, 2026 | 385 ms |
| Oct 3, 2026 | 380 ms |
| Oct 10, 2026 | 376 ms |
| Oct 17, 2026 | 378 ms |
| Oct 24, 2026 | 382 ms |
| Oct 31, 2026 | 388 ms |
| Nov 7, 2026 | 394 ms |
| Nov 14, 2026 | 397 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
Speed
Use efficient cache lifetimes
2.6 s · 2.4 MB75 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).
Reduce unused JavaScript
2.9 s · 609 KiBAbout 609 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Improve image delivery
1.9 s · 369 KiB4 images could be 369 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,350 HTML elements
The page has 6,350 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 6.1 s
A phone's processor spends 6.1 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.
Document request latency
700 msThe HTML itself could arrive about 700 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
695 msReduce initial server response time. Google estimates savings of 695 ms on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, trustmate.pro and getzowie.com and others), adding 1.1 MB and 313 ms of main-thread time.
Google Tag Manager adds 307 ms
307 msGoogle Tag Manager costs a phone 307 ms of main-thread work and 702 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.
Server response: 795 ms
795 msYour server takes 795 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Google Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 299 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.
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.
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 LCP: 4.9 s
4.9 sReal visitors wait 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.38
0.38For real visitors the layout shifts by 0.38 (75th percentile). Good is under 0.1.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 21.3 s
21.3 sYour largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “null”.
Time to Interactive: 25.4 s
25.4 sThe page becomes fully interactive after 25.4 s. Good is under 3.8 s.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Real-user INP: 486 ms
486 msReal visitors wait 486 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 107% slower for real visitors
+107%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 191 ms to 397 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 96% slower for real visitors
+96%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.2 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.183
0.183The layout shifts by 0.183 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 checks passed
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 6.1 MB in 240 requests
6.1 MBYour homepage downloads 6.1 MB in 240 requests on a phone: images 3.2 MB (95), scripts 2.0 MB (94) and fonts 644 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.74 g of CO₂e: 209.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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 text element with low contrast
1 text element doesn'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.
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.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (3 elements).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 240 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
473 internal links, 0 external
The homepage links to 473 pages on gino-rossi.com and 0 external pages.
7 checks passed
Meta description: 125 characters
Your meta description is 125 characters: “Sprawdź asortyment stylowej marki Gino Rossi w CCC. Największy wybór wysokiej jakości butów, torebek i akcesoriów Gino …”.
One H1 headline
Your main headline reads: “Gino Rossi”.
Title: 47 characters
Your title is a healthy 47 characters: “Gino Rossi - Buty, torebki i akcesoria - CCC.eu”.
Canonical URL set
The canonical URL is https://ccc.eu/pl/pl/c/marki/gino-rossi.
Structured data in place
Structured data found: OnlineStore 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://ccc.eu/bg/bg/sitemap-categories.xml.
AI search readiness
No llms.txt
There is no https://ccc.eu/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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,182 words), so crawlers that don't run JavaScript still read it.
Other pages
14 linked pages hidden from search
https://ccc.eu/pl/pl/lp/regulamin-polityki-prywatnosci-13-02-2026, https://ccc.eu/pl/pl/c/nowa-kolekcja/kobieta/kolekcja-jesien-zima, https://ccc.eu/pl/pl/c/kobieta/nowosci, https://ccc.eu/pl/pl/c/nowa-kolekcja/buty-kobieta/kolekcja-jesien-zima, https://ccc.eu/pl/pl/c/nowa-kolekcja/torebki-kobieta/kolekcja-jesien-zima and https://ccc.eu/pl/pl/c/nowa-kolekcja/akcesoria-kobieta/kolekcja-jesien-zima and 8 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
4 pages share a title
https://ccc.eu/pl/pl/c/nowa-kolekcja/kobieta/kolekcja-jesien-zima, https://ccc.eu/pl/pl/c/nowa-kolekcja/buty-kobieta/kolekcja-jesien-zima, https://ccc.eu/pl/pl/c/nowa-kolekcja/torebki-kobieta/kolekcja-jesien-zima and https://ccc.eu/pl/pl/c/nowa-kolekcja/akcesoria-kobieta/kolekcja-jesien-zima all use the title “Kolekcja Jesień-Zima - CCC.eu”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://ccc.eu/pl/pl/c/nowa-kolekcja/kobieta/kolekcja-jesien-zima, https://ccc.eu/pl/pl/c/nowa-kolekcja/buty-kobieta/kolekcja-jesien-zima, https://ccc.eu/pl/pl/c/nowa-kolekcja/torebki-kobieta/kolekcja-jesien-zima and https://ccc.eu/pl/pl/c/nowa-kolekcja/akcesoria-kobieta/kolekcja-jesien-zima use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://ccc.eu/pl/pl/lp/regulamin-polityki-prywatnosci-13-02-2026 has no <h1> headline, so visitors and search engines get no clear main topic.
8 pages slow to respond
https://ccc.eu/pl/pl/c/kobieta/nowosci, https://ccc.eu/pl/pl/c/nowa-kolekcja/buty-kobieta/kolekcja-jesien-zima, https://ccc.eu/pl/pl/c/nowa-kolekcja/torebki-kobieta/kolekcja-jesien-zima, https://ccc.eu/pl/pl/c/nowa-kolekcja/akcesoria-kobieta/kolekcja-jesien-zima, https://ccc.eu/pl/pl/c/kobieta/nowosci/bhpc and https://ccc.eu/pl/pl/c/kobieta/nowosci/gino-rossi and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 200 found) and read each the way a search engine does.
4 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
22 of 24 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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 816 words of copy
The homepage carries about 816 words of visible text.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
3 other companies contacted
Loading the homepage contacts 3 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 gino-rossi.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Angular
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on gino-rossi.com, including 26 speed issues, 3 SEO issues and 7 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.