Website review, no card needed
astadelmobile.it website review
Visit site (opens in a new tab)Reviewed 23 October 202639 issues · 84 checks
This review found 39 issues worth fixing on astadelmobile.it, 17 of them high impact, across 84 checks. The most urgent: render-blocking 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 918 ms |
| May 9, 2026 | 918 ms |
| May 16, 2026 | 902 ms |
| May 23, 2026 | 907 ms |
| May 30, 2026 | 921 ms |
| Jun 6, 2026 | 924 ms |
| Jun 13, 2026 | 955 ms |
| Jun 20, 2026 | 937 ms |
| Jun 27, 2026 | 930 ms |
| Jul 4, 2026 | 925 ms |
| Jul 11, 2026 | 926 ms |
| Jul 18, 2026 | 918 ms |
| Jul 25, 2026 | 922 ms |
| Aug 1, 2026 | 933 ms |
| Aug 8, 2026 | 934 ms |
| Aug 15, 2026 | 952 ms |
| Aug 22, 2026 | 956 ms |
| Aug 29, 2026 | 939 ms |
| Sep 5, 2026 | 950 ms |
| Sep 12, 2026 | 950 ms |
| Sep 19, 2026 | 963 ms |
| Sep 26, 2026 | 968 ms |
| Oct 3, 2026 | 977 ms |
| Oct 10, 2026 | 984 ms |
| Oct 17, 2026 | 978 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 88 ms |
| May 9, 2026 | 87 ms |
| May 16, 2026 | 85 ms |
| May 23, 2026 | 86 ms |
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 85 ms |
| Jun 13, 2026 | 86 ms |
| Jun 20, 2026 | 84 ms |
| Jun 27, 2026 | 83 ms |
| Jul 4, 2026 | 83 ms |
| Jul 11, 2026 | 84 ms |
| Jul 18, 2026 | 86 ms |
| Jul 25, 2026 | 86 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 88 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 89 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 86 ms |
| Sep 26, 2026 | 86 ms |
| Oct 3, 2026 | 85 ms |
| Oct 10, 2026 | 87 ms |
| Oct 17, 2026 | 87 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.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.6 s
6.4 s
Speed
Render-blocking requests
12.9 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 12.9 s.
Use efficient cache lifetimes
9.8 s · 1.8 MB44 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Reduce unused CSS
8.4 s · 1.6 MBAbout 1.6 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.4 s faster on a phone.
Minify CSS
4.5 s · 890 KiB890 KiB could be saved by minifying CSS.
Reduce unused JavaScript
2.3 s · 358 KiBAbout 358 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Mobile performance score: 41
41/100Your mobile performance score is 41 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Font display
600 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).
Minify JavaScript
450 ms · 63 KiB63 KiB could be saved by minifying JavaScript.
Improve image delivery
300 ms · 177 KiB5 images could be 177 KiB 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.
Document request latency
83 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need.
3 third-party services on the page
3 third-party services load with your homepage (JSDelivr CDN, Google Fonts and esm.sh), adding 155 KiB and 9 ms of main-thread time.
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.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 92 ms of it running JavaScript. That is comfortably low.
Server response: 231 ms
231 msYour server sent the HTML in 231 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 14.0 s
14.0 sThe first text or image appears after 14.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 23.9 s
23.9 sYour largest element takes 23.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “...”.
Speed Index: 14.0 s
14.0 sVisually, the page fills in at 14.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.0 s
24.0 sThe page becomes fully interactive after 24.0 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.279
0.279The layout shifts by 0.279 while loading, so content jumps under the reader's thumb. Good is under 0.1.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 88 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 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: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 106 ms
106 msReal visitors wait 106 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 524 ms
524 msReal visitors wait 524 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.0 MB in 59 requests
4.0 MBYour homepage downloads 4.0 MB in 59 requests on a phone: stylesheets 1.6 MB (4), fonts 857 KiB (5) and images 725 KiB (16). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
divani-blu-hp-m.webp 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 1.1 g of CO₂ per visit
1.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.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
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Headings skip levels
Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (362 characters)
Your meta description is 362 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.
71 internal links, 3 external
The homepage links to 71 pages on astadelmobile.it and 3 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Designe qualità”.
Title: 38 characters
Your title is a healthy 38 characters: “L'arredamento Italiano | Astadelmobile”.
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.astadelmobile.it/XMLDOC/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.astadelmobile.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.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (292 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.astadelmobile.it/c/promozioni/in-corso and https://www.astadelmobile.it/c/primo-prezzo/offerte-arredi-made-in-italy all use the title “Forbidden”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.astadelmobile.it/c/promozioni/in-corso and https://www.astadelmobile.it/c/primo-prezzo/offerte-arredi-made-in-italy have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages share a meta description
https://www.astadelmobile.it/c/cucina/ad-angolo-a-isola-componibile, https://www.astadelmobile.it/c/divani/e-relax-per-un-soggiorno-di-design-e-confortevole, https://www.astadelmobile.it/c/zona-giorno/arredi-funzionali-per-il-soggiorno-di-casa-tua, https://www.astadelmobile.it/c/tavoli-sedie/arredo-pranzo, https://www.astadelmobile.it/c/notte/zona-notte-dove-i-sogni-hanno-inizio and https://www.astadelmobile.it/c/complementi/arredo-che-rendono-unica-la-tua-casa and 7 others use the same meta description. A description written for each page earns more clicks.
2 pages with very little text
https://www.astadelmobile.it/c/promozioni/in-corso and https://www.astadelmobile.it/c/primo-prezzo/offerte-arredi-made-in-italy have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 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.
Every page has an H1
Each page we checked has a main headline.
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://www.astadelmobile.it/Images/hp-zona-notte-m.webp.
14 small tap targets
14 of 22 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.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Manifest: Line: 3, column: 1, Syntax error.”.
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.
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.
Only about 233 words
The homepage has only about 233 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
1 short form
A short form (2 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
4 other companies contacted
Loading the homepage contacts 4 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 astadelmobile.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Visual Studio 2022
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on astadelmobile.it, including 15 speed issues, 3 SEO issues and 5 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.