Website review, no card needed
margraf.it website review
Visit site (opens in a new tab)Reviewed 18 October 202644 issues · 81 checks
This review found 44 issues worth fixing on margraf.it, 22 of them high impact, across 81 checks. The most urgent: avoid multiple page redirects. 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) |
|---|---|
| Apr 25, 2026 | 2.2 s |
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 181 ms |
| May 2, 2026 | 182 ms |
| May 9, 2026 | 184 ms |
| May 16, 2026 | 186 ms |
| May 23, 2026 | 208 ms |
| May 30, 2026 | 216 ms |
| Jun 6, 2026 | 212 ms |
| Jun 13, 2026 | 210 ms |
| Jun 20, 2026 | 202 ms |
| Jun 27, 2026 | 203 ms |
| Jul 4, 2026 | 205 ms |
| Jul 11, 2026 | 207 ms |
| Jul 18, 2026 | 213 ms |
| Jul 25, 2026 | 202 ms |
| Aug 1, 2026 | 197 ms |
| Aug 8, 2026 | 194 ms |
| Aug 15, 2026 | 202 ms |
| Aug 22, 2026 | 205 ms |
| Aug 29, 2026 | 205 ms |
| Sep 5, 2026 | 202 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 199 ms |
| Oct 10, 2026 | 201 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
Avoid multiple page redirects
29.3 sThe page goes through 1 redirect before it starts loading, costing about 29.3 s. Link and advertise the final URL directly.
Reduce unused JavaScript
9.7 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.7 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 47). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google Fonts and others), adding 2.1 MB and 156 ms of main-thread time.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 270 ms. During a long task the page ignores taps.
Google Tag Manager adds 120 ms
120 msGoogle Tag Manager costs a phone 120 ms of main-thread work and 519 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.
thron.com adds 0 ms
0 msthron.com costs a phone 0 ms of main-thread work and 1.5 MB 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.
Reduce unused CSS
150 ms · 142 KiBAbout 142 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 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.
Real-user CLS: 1.00
1.00For real visitors the layout shifts by 1.00 (75th percentile). Good is under 0.1.
First Contentful Paint: 12.8 s
12.8 sThe first text or image appears after 12.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 67.4 s
67.4 sYour largest element takes 67.4 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 16.4 s
16.4 sVisually, the page fills in at 16.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 70.3 s
70.3 sThe page becomes fully interactive after 70.3 s. Good is under 3.8 s.
Total Blocking Time: 706 ms
706 msScripts block taps and scrolling for 706 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 287 ms
287 msReal visitors wait 287 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
3 images without width and height
3 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-10-10, real Chrome visitors' tap response (inp) went from 181 ms to 201 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 611 ms
611 msReal visitors wait 611 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 24.8 MB in 126 requests
24.8 MBYour homepage downloads 24.8 MB in 126 requests on a phone: images 21.5 MB (44), scripts 2.7 MB (41) and other files 358 KiB (13). Under 2 MB keeps phones on slow connections fast.
17 images over 500 KB
17 images weigh 18.6 MB together. On a phone connection a single image that size takes seconds.
21 images far larger than shown
17.3 MB21 images are downloaded at several times the size a phone draws them, for example verde-alpi.jpeg at 1,920 px wide, shown at 201 px. Resized copies would save about 17.3 MB.
21 images in older formats
21 images (20.0 MB) 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.
9 images below the first screen load straight away
9 images further down the page (7.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 7.0 g of CO₂ per visit
7.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.02 g of CO₂e: 842.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 buttons without a name
5 buttons have no accessible name, so screen readers announce just “button”.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (25 elements)
All page content should be contained by landmarks: 25 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (12 elements)
Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 10 failed. 2 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
30 internal links, 8 external
The homepage links to 30 pages on margraf.it and 8 external pages.
6 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Trasformiamo il marmo in architettura dal 1906. Scopri oltre 400 tipi di marmo e pietre da tutto il mondo e i progetti …”.
Title: 57 characters
Your title is a healthy 57 characters: “Lavorazione marmi per architettura e design | Margraf Spa”.
Canonical URL set
The canonical URL is https://www.margraf.it/it/.
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.margraf.it/sitemap_index.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.margraf.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 (394 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages are broken
Your homepage links to https://www.margraf.it/it/prodotti and https://www.margraf.it/it/news/marmomac-2026-una-storia-lunga-120-anni, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages share a title
/ and https://www.margraf.it/it all use the title “Lavorazione marmi per architettura e design | Margraf Spa”. Search engines can't tell which page to show for a search, so each competes with the others.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.margraf.it/it/collaborazioni, whose canonical is https://www.margraf.it/it/collaborazioni/gg-loop. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.margraf.it/it has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.margraf.it/it/progetti and https://www.margraf.it/it/collaborazioni 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 20 found) and read each the way a search engine does.
3 checks passed
Every page has a meta description
All 13 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 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 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
24 of 28 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 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 480 words of copy
The homepage carries about 480 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Area download”.
1 short form
A short form (7 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 margraf.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Analytics
- Google Tag Manager
- Hosting
- Netlify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on margraf.it, including 18 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.