Website review, no card needed
bigmat.it website review
Visit site (opens in a new tab)Reviewed 19 October 202648 issues · 91 checks
This review found 48 issues worth fixing on bigmat.it, 19 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
65D- #108,859 of 117,262 reviewed websitesbeats 6%
- #64,529 of 66,884 online storesbeats 3%
- #136 of 166 PrestaShop storesbeats 15%
Closest competitors among PrestaShop stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.8 s |
| May 2, 2026 | 5.1 s |
| May 9, 2026 | 5.2 s |
| May 16, 2026 | 4.8 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.4 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.7 s |
| Aug 29, 2026 | 5.5 s |
| Sep 5, 2026 | 5.7 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 197 ms |
| May 2, 2026 | 199 ms |
| May 9, 2026 | 206 ms |
| May 16, 2026 | 207 ms |
| May 23, 2026 | 213 ms |
| May 30, 2026 | 221 ms |
| Jun 6, 2026 | 221 ms |
| Jun 13, 2026 | 229 ms |
| Jun 20, 2026 | 229 ms |
| Jun 27, 2026 | 230 ms |
| Jul 4, 2026 | 230 ms |
| Jul 11, 2026 | 226 ms |
| Jul 18, 2026 | 224 ms |
| Jul 25, 2026 | 221 ms |
| Aug 1, 2026 | 230 ms |
| Aug 8, 2026 | 239 ms |
| Aug 15, 2026 | 245 ms |
| Aug 22, 2026 | 243 ms |
| Aug 29, 2026 | 239 ms |
| Sep 5, 2026 | 237 ms |
| Sep 12, 2026 | 241 ms |
| Sep 19, 2026 | 241 ms |
| Sep 26, 2026 | 242 ms |
| Oct 3, 2026 | 242 ms |
| Oct 10, 2026 | 235 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
Improve image delivery
11.9 s · 3.6 MB22 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.9 s faster on a phone.
Use efficient cache lifetimes
8.0 s · 2.2 MB131 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Reduce unused JavaScript
4.7 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.
Render-blocking requests
3.0 s52 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 63). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.2 MB and 1.5 s of main-thread time.
Google Tag Manager adds 644 ms
644 msGoogle Tag Manager costs a phone 644 ms of main-thread work and 693 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.
Google CDN adds 508 ms
508 msGoogle CDN costs a phone 508 ms of main-thread work and 1.1 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
450 ms · 87 KiBAbout 87 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.
Minify JavaScript
300 ms · 34 KiB34 KiB could be saved by minifying JavaScript.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 285 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 9 KiB9 KiB could be saved by minifying CSS.
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 63 but mobile only 37. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 214 ms
214 msYour server sent the HTML in 214 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: 32.9 s
32.9 sYour largest element takes 32.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MatTony presenta il prodotto del mese: il soffione doccia "…”.
Speed Index: 21.1 s
21.1 sVisually, the page fills in at 21.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 39.7 s
39.7 sThe page becomes fully interactive after 39.7 s. Good is under 3.8 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 886 ms
886 msScripts block taps and scrolling for 886 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 242 ms
242 msReal visitors wait 242 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 197 ms to 235 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Largest content (LCP) got 42% faster for real visitors
-42%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
Images and page weight
Page weight: 8.1 MB in 180 requests
8.1 MBYour homepage downloads 8.1 MB in 180 requests on a phone: images 4.4 MB (28), scripts 2.6 MB (69) and other files 406 KiB (17). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.
1 image far larger than shown
731 KiB1 image is downloaded at several times the size a phone draws it, for example Banner_Color interior Kerakoll_2026_Mobile.jpg at 3,646 px wide, shown at 331 px. Resized copies would save about 731 KiB.
20 images in older formats
20 images (4.3 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.
An image on the first screen is lazy-loaded
Banner_Color interior Kerakoll_2026_Mobile.jpg 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).
2 images below the first screen load straight away
2 images further down the page (957 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.30 g of CO₂e: 275.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (3 elements)
Contentinfo landmark should not be contained in another landmark: 3 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 (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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 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 25 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.
82 internal links, 15 external
The homepage links to 82 pages on bigmat.it and 15 external pages.
7 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Tutto il necessario per costruire e ristrutturare, per i professionisti dell'edilizia, in tutta Italia. Colorifici, sho…”.
One H1 headline
Your main headline reads: “Bigmat”.
Title: 53 characters
Your title is a healthy 53 characters: “BigMat | Rivendite edili di materiali in tutta Italia”.
Canonical URL set
The canonical URL is https://www.bigmat.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.bigmat.it/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.bigmat.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 (770 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages slow to respond
https://www.bigmat.it/content/80-iniziative, https://www.bigmat.it/content/219-bigmat-sponsor-ufficiale-delle-nazionali-di-pallavolo, https://www.bigmat.it/content/83-bigmat-international-architecture-award, https://www.bigmat.it/content/84-costruiamo-per-lo-sport, https://www.bigmat.it/content/185-bigcard and https://www.bigmat.it/novita and 6 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 39 found) and read each the way a search engine does.
7 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.
Titles are unique
Every page we checked has its own title.
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
3 broken images
3 images failed to load on a phone, for example https://www.bigmat.it/.
37 small tap targets
37 of 66 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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: 3 testimonial or review blocks. 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 712 words of copy
The homepage carries about 712 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: iubenda
A consent management tool (iubenda) 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 bigmat.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- PrestaShop
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on bigmat.it, including 24 speed issues, 1 SEO issue 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.