Website review, no card needed

rematarlazzi.it logo

rematarlazzi.it website review

Visit site (opens in a new tab)Reviewed 4 November 202644 issues · 86 checks

This review found 44 issues worth fixing on rematarlazzi.it, 13 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.2 s2.9 sMay 16Oct 313.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.1 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Oct 31, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
148 ms133 msMay 16Oct 31138 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026135 ms
May 23, 2026139 ms
May 30, 2026139 ms
Jun 6, 2026143 ms
Jun 13, 2026144 ms
Jun 20, 2026143 ms
Jun 27, 2026144 ms
Jul 4, 2026145 ms
Jul 11, 2026144 ms
Jul 18, 2026146 ms
Jul 25, 2026145 ms
Aug 1, 2026143 ms
Aug 8, 2026142 ms
Aug 15, 2026141 ms
Aug 22, 2026139 ms
Aug 29, 2026141 ms
Sep 5, 2026137 ms
Sep 12, 2026138 ms
Sep 19, 2026139 ms
Sep 26, 2026136 ms
Oct 3, 2026139 ms
Oct 10, 2026137 ms
Oct 17, 2026140 ms
Oct 24, 2026137 ms
Oct 31, 2026138 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

Full-page screenshot of rematarlazzi.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rematarlazzi.it at 2.0 s2.0 s
  2. rematarlazzi.it at 4.0 s4.0 s
  3. rematarlazzi.it at 6.0 s6.0 s
  4. rematarlazzi.it at 8.0 s8.0 s
  5. rematarlazzi.it at 10.0 s10.0 s
  6. rematarlazzi.it at 12.0 s12.0 s
  7. rematarlazzi.it at 14.0 s14.0 s
  8. rematarlazzi.it at 16.0 s16.0 s

Speed

11 to fix60
  • Render-blocking requests

    3.0 s

    20 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.

  • Improve image delivery

    600 ms · 2.5 MB

    12 images could be 2.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.

  • Reduce unused CSS

    900 ms · 140 KiB

    About 140 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

  • Document request latency

    800 ms

    The HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    775 ms

    Reduce initial server response time. Google estimates savings of 775 ms on a phone.

  • Font display

    700 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).

  • Reduce unused JavaScript

    300 ms · 92 KiB

    About 92 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 1,766 HTML elements

    The page has 1,766 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Server response: 875 ms

    875 ms

    Your server takes 875 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Google Tag Manager adds 0 ms

    0 ms

    Google Tag Manager costs a phone 0 ms of main-thread work and 325 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Cookiebot, Google Fonts and Google Tag Manager and others), adding 543 KiB and 217 ms of main-thread time.

  • Use efficient cache lifetimes

    50 ms · 34 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (34 KiB).

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 78 ms. During a long task the page ignores taps.

  • Minify CSS

    11 KiB

    11 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.

1 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 311 ms of it running JavaScript. That is comfortably low.

Core Web Vitals

10 to fix33
  • 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: 0.36

    0.36

    For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 15.4 s

    15.4 s

    Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “RemaTarlazzi - materiale elettrico, illuminazione, automazi…”. Most of its time is element render delay (7.6 s).

  • Speed Index: 13.9 s

    13.9 s

    Visually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 16.1 s

    16.1 s

    The page becomes fully interactive after 16.1 s. Good is under 3.8 s.

  • First Contentful Paint: 3.2 s

    3.2 s

    The first text or image appears after 3.2 s on a phone. Good is under 1.8 s.

  • Real-user LCP: 3.3 s

    3.3 s

    Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.5 s

    2.5 s

    Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.4 s

    1.4 s

    Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 135 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 149 ms

    149 ms

    Real visitors wait 149 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 39 ms

    39 ms

    Scripts block the page for only 39 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix60
  • Page weight: 5.5 MB in 97 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 97 requests on a phone: images 4.2 MB (29), scripts 884 KiB (42) and fonts 202 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    9 KiB

    1 image is downloaded at several times the size a phone draws it, for example certificazioni.png at 851 px wide, shown at 270 px. Resized copies would save about 9 KiB.

  • 6 images in older formats

    6 images (344 KiB) 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.

  • 3 images below the first screen load straight away

    3 images further down the page (205 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.55 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.55 g of CO₂e: 186.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

9 to fixGoogle 8889
  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 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.

  • 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.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 form fields without a label

    8 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 46 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: 46 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10085
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “RemaTarlazzi | Multispecialisti in Materiale Elettrico & Illuminazione”.

  • 3 H1 headlines

    There are 3 <h1> headlines (“100 ANNI DI INNOVAZIONE”, “RemaTarlazzi - materiale elettrico, illuminazione…” and “Formazione tecnica”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 119 internal links, 14 external

    The homepage links to 119 pages on rematarlazzi.it and 14 external pages.

5 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Multispecialisti nella distribuzione di materiale elettrico, illuminazione, automazione, sicurezza e energie rinnovabil…”.

  • Canonical URL set

    The canonical URL is https://www.rematarlazzi.it/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.rematarlazzi.it/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.rematarlazzi.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 sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,090 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.rematarlazzi.it/integra-il-software-erp-che-velocizza-il-tuo-lavoro-rendendolo-smart has no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 links to non-canonical URLs

    Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://www.rematarlazzi.it/index.php/profilo-aziendale, whose canonical is https://www.rematarlazzi.it/profilo-aziendale. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page slow to respond

    https://www.rematarlazzi.it/index.php/rematarlazzi-facile took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 83 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.

  • 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

2 to fixGoogle 9687
  • 4 small tap targets

    4 of 13 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 (Not Found)”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 12-field form

    Your longest form asks for 12 fields (4 required). Every extra field lowers completion.

  • 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 637 words of copy

    The homepage carries about 637 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 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.

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 rematarlazzi.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2019.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Asn Ibsnaz

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 rematarlazzi.it, including 21 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25