Website review, no card needed
arcaplanet.it website review
Visit site (opens in a new tab)Reviewed 1 November 202637 issues · 81 checks
This review found 37 issues worth fixing on arcaplanet.it, 16 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 185 ms |
| May 16, 2026 | 186 ms |
| May 23, 2026 | 187 ms |
| May 30, 2026 | 189 ms |
| Jun 6, 2026 | 193 ms |
| Jun 13, 2026 | 195 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 197 ms |
| Jul 4, 2026 | 199 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 204 ms |
| Jul 25, 2026 | 206 ms |
| Aug 1, 2026 | 206 ms |
| Aug 8, 2026 | 206 ms |
| Aug 15, 2026 | 207 ms |
| Aug 22, 2026 | 205 ms |
| Aug 29, 2026 | 204 ms |
| Sep 5, 2026 | 204 ms |
| Sep 12, 2026 | 206 ms |
| Sep 19, 2026 | 209 ms |
| Sep 26, 2026 | 211 ms |
| Oct 3, 2026 | 210 ms |
| Oct 10, 2026 | 208 ms |
| Oct 17, 2026 | 208 ms |
| Oct 24, 2026 | 207 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
4.2 s · 725 KiBAbout 725 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 451 KiB11 files are served with short cache lifetimes, so returning visitors download them again (451 KiB).
Improve image delivery
600 ms · 6.5 MB21 images could be 6.5 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.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Maps adds 100 ms
100 msGoogle Maps costs a phone 100 ms of main-thread work and 378 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 (PayPal, Google Maps and Dynamic Yield and others), adding 981 KiB and 388 ms of main-thread time.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 156 ms. During a long task the page ignores taps.
Duplicated JavaScript
150 ms · 5 KiB5 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
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 JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 928 ms of it running JavaScript. That is comfortably low.
Server response: 31 ms
31 msYour server sent the HTML in 31 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.
Largest Contentful Paint: 26.7 s
26.7 sYour largest element takes 26.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hero carousel image”.
Time to Interactive: 27.5 s
27.5 sThe page becomes fully interactive after 27.5 s. Good is under 3.8 s.
First Contentful Paint: 6.7 s
6.7 sThe first text or image appears after 6.7 s on a phone. Good is under 1.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
Real-user INP: 227 ms
227 msReal visitors wait 227 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 185 ms to 207 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 571 ms
571 msReal visitors wait 571 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 75 ms
75 msScripts block the page for only 75 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.5 MB in 113 requests
9.5 MBYour homepage downloads 9.5 MB in 113 requests on a phone: images 6.8 MB (42), scripts 1.4 MB (31) and fonts 1.1 MB (12). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.
9 images far larger than shown
4.0 MB9 images are downloaded at several times the size a phone draws them, for example 5ff9d00b-2d00-492e-ba3c-50636ad29e79___d9c89a17d3ec78e1b687a at 2,700 px wide, shown at 118 px. Resized copies would save about 4.0 MB.
7 images below the first screen load straight away
7 images further down the page (2.8 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
be7ba317-b856-47ed-9876-0b0dd6eb4968___6c42b5a25667f7771bd4b 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: 324.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Required ARIA attributes must be provided (1 element)
Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 22 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 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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 H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (167 characters)
Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
44 internal links, 26 external
The homepage links to 44 pages on arcaplanet.it and 26 external pages.
4 checks passed
Title: 65 characters
Your title is a healthy 65 characters: “Cibo e accessori per cani, gatti e animali domestici | Arcaplanet”.
Canonical URL set
The canonical URL is https://www.arcaplanet.it/.
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.arcaplanet.it/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.
No llms.txt
There is no https://www.arcaplanet.it/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.
2 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 (309 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a title
https://www.arcaplanet.it/promozioni-negozio, https://www.arcaplanet.it/promozioni-online, https://www.arcaplanet.it/prezzi-bassi-garantiti, https://www.arcaplanet.it/programmadieteleggere, https://www.arcaplanet.it/click-and-collect-ordina-online-e-ritira-gratis-in-un-negozio-arcaplanet and https://www.arcaplanet.it/arcaplanet-pet-wash-scopri-il-servizio-di-lavaggio-esclusivo-nei-pet-store and 9 others have no <title>, so Google invents the link text in results.
15 pages without a meta description
https://www.arcaplanet.it/promozioni-negozio, https://www.arcaplanet.it/promozioni-online, https://www.arcaplanet.it/prezzi-bassi-garantiti, https://www.arcaplanet.it/programmadieteleggere, https://www.arcaplanet.it/click-and-collect-ordina-online-e-ritira-gratis-in-un-negozio-arcaplanet and https://www.arcaplanet.it/arcaplanet-pet-wash-scopri-il-servizio-di-lavaggio-esclusivo-nei-pet-store and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.arcaplanet.it/promozioni-negozio, https://www.arcaplanet.it/promozioni-online, https://www.arcaplanet.it/prezzi-bassi-garantiti, https://www.arcaplanet.it/programmadieteleggere, https://www.arcaplanet.it/click-and-collect-ordina-online-e-ritira-gratis-in-un-negozio-arcaplanet and https://www.arcaplanet.it/arcaplanet-pet-wash-scopri-il-servizio-di-lavaggio-esclusivo-nei-pet-store and 9 others 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 31 found) and read each the way a search engine does.
3 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
8 small tap targets
8 of 39 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.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of null (reading 'innerHTML')”.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 6 trust badges. 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 458 words of copy
The homepage carries about 458 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 arcaplanet.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on arcaplanet.it, including 13 speed issues, 5 SEO issues and 4 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.