Website review, no card needed
materese.com website review
Visit site (opens in a new tab)Reviewed 16 November 202641 issues · 83 checks
This review found 41 issues worth fixing on materese.com, 10 of them high impact, across 83 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 827 ms |
| Jun 6, 2026 | 845 ms |
| Jun 13, 2026 | 876 ms |
| Jun 20, 2026 | 855 ms |
| Jun 27, 2026 | 861 ms |
| Jul 4, 2026 | 833 ms |
| Jul 11, 2026 | 812 ms |
| Jul 18, 2026 | 834 ms |
| Jul 25, 2026 | 835 ms |
| Aug 1, 2026 | 866 ms |
| Aug 8, 2026 | 869 ms |
| Aug 15, 2026 | 873 ms |
| Aug 22, 2026 | 873 ms |
| Aug 29, 2026 | 861 ms |
| Sep 5, 2026 | 904 ms |
| Sep 12, 2026 | 953 ms |
| Sep 19, 2026 | 968 ms |
| Sep 26, 2026 | 989 ms |
| Oct 3, 2026 | 972 ms |
| Oct 10, 2026 | 942 ms |
| Oct 17, 2026 | 974 ms |
| Oct 24, 2026 | 971 ms |
| Oct 31, 2026 | 977 ms |
| Nov 7, 2026 | 1.0 s |
| Nov 14, 2026 | 977 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 88 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 90 ms |
| Jun 27, 2026 | 88 ms |
| Jul 4, 2026 | 89 ms |
| Jul 11, 2026 | 88 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 89 ms |
| Aug 15, 2026 | 91 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 92 ms |
| Sep 5, 2026 | 93 ms |
| Sep 12, 2026 | 93 ms |
| Sep 19, 2026 | 94 ms |
| Sep 26, 2026 | 93 ms |
| Oct 3, 2026 | 91 ms |
| Oct 10, 2026 | 89 ms |
| Oct 17, 2026 | 88 ms |
| Oct 24, 2026 | 89 ms |
| Oct 31, 2026 | 89 ms |
| Nov 7, 2026 | 89 ms |
| Nov 14, 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.4 s
0.8 s
1.2 s
1.6 s
1.9 s
2.3 s
2.7 s
3.1 s
Speed
Improve image delivery
3.1 s · 4.6 MB20 images could be 4.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.
Render-blocking requests
1.8 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused JavaScript
1.2 s · 231 KiBAbout 231 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Use efficient cache lifetimes
800 ms · 884 KiB139 files are served with short cache lifetimes, so returning visitors download them again (884 KiB).
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Font display
900 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).
iubenda adds 363 ms
363 msiubenda costs a phone 363 ms of main-thread work and 135 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.
4 third-party services on the page
4 third-party services load with your homepage (iubenda, jQuery CDN and Google Fonts and others), adding 357 KiB and 397 ms of main-thread time.
Minify JavaScript
150 ms · 44 KiB44 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 109 ms. During a long task the page ignores taps.
Reduce unused CSS
35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 538 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 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: 27.8 s
27.8 sYour largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 29.6 s
29.6 sThe page becomes fully interactive after 29.6 s. Good is under 3.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
57 images without width and height
57 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.108
0.108The layout shifts by 0.108 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, 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) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.8 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 93 ms
93 msReal visitors wait 93 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 105 ms
105 msScripts block the page for only 105 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.6 MB in 153 requests
8.6 MBYour homepage downloads 8.6 MB in 153 requests on a phone: images 8.0 MB (129), scripts 464 KiB (10) and fonts 111 KiB (6). Under 2 MB keeps phones on slow connections fast.
16 images far larger than shown
4.8 MB16 images are downloaded at several times the size a phone draws them, for example 5084-1752052375.jpeg at 2,560 px wide, shown at 369 px. Resized copies would save about 4.8 MB.
4 images over 500 KB
4 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.
36 images in older formats
36 images (7.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.
32 images below the first screen load straight away
32 images further down the page (6.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.4 g of CO₂ per visit
2.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.45 g of CO₂e: 293.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (129 elements)
All page content should be contained by landmarks: 129 elements on the page fail this check, rated moderate by axe-core.
98 links without text
98 visible links have no text or label, so screen readers cannot say where they go.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“Ultimi arrivi”, “Outlet” and “In primo piano”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.materese.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at materese.com/robots.txt, the first file search crawlers ask for.
4 links crawlers can't follow
4 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.
233 internal links, 14 external
The homepage links to 233 pages on materese.com and 14 external pages.
2 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Siamo un negozio di Genova e ci occupiamo dell'infanzia da tanto tempo oltre 50 anni allora era tutto diverso: non…”.
Title: 32 characters
Your title is a healthy 32 characters: “Materese - Centro prima infanzia”.
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.materese.com/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (722 words), so crawlers that don't run JavaScript still read it.
Other pages
16 pages share a title
https://www.materese.com/IT/index.html, https://www.materese.com/IT/shoppingcart.html, https://www.materese.com/EN/index.html, https://www.materese.com/IT/categorie/9/la_puericultura_leggera.html, https://www.materese.com/IT/sottocategorie/23/igiene_amp_benessere.html and https://www.materese.com/IT/sottocategorie/24/sicurezza.html and 10 others all use the title “Materese - Centro prima infanzia”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages share a meta description
https://www.materese.com/IT/shoppingcart.html, https://www.materese.com/IT/categorie/9/la_puericultura_leggera.html, https://www.materese.com/IT/sottocategorie/23/igiene_amp_benessere.html, https://www.materese.com/IT/sottocategorie/24/sicurezza.html, https://www.materese.com/IT/sottocategorie/25/allattamento_amp_pappa.html and https://www.materese.com/IT/categorie/10/a_passeggio.html and 8 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 106 found) and read each the way a search engine does.
6 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 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
39 small tap targets
39 of 85 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 491 words of copy
The homepage carries about 491 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
2 calls to action
The homepage has 2 calls to action, for example “Contact Us”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: iubenda
A consent management tool (iubenda) loads with the page.
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 materese.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
- jQuery
- Hosting
- Aruba S.p.A.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on materese.com, including 18 speed issues, 7 SEO issues and 2 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.