Website review, no card needed

diapro.it logo

diapro.it website review

Visit site (opens in a new tab)Reviewed 18 October 202643 issues · 84 checks

This review found 43 issues worth fixing on diapro.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.

  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
5.8 s3.5 sApr 25Oct 104.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.8 s
May 2, 20263.8 s
May 9, 20264.2 s
May 16, 20264.7 s
May 23, 20264.9 s
May 30, 20264.9 s
Jun 6, 20265.1 s
Jun 13, 20264.6 s
Jun 20, 20264.7 s
Jun 27, 20264.9 s
Jul 4, 20264.2 s
Jul 11, 20264.4 s
Jul 18, 20264.1 s
Jul 25, 20264.0 s
Aug 1, 20264.3 s
Aug 8, 20264.7 s
Aug 15, 20264.9 s
Aug 22, 20265.1 s
Aug 29, 20265.5 s
Sep 5, 20265.2 s
Sep 12, 20265.0 s
Sep 19, 20265.0 s
Sep 26, 20265.0 s
Oct 3, 20265.0 s
Oct 10, 20264.9 s
Real-visitor tap response (INP)75th percentile, phones
202 ms74 msApr 25Oct 1095 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026121 ms
May 2, 2026119 ms
May 9, 2026104 ms
May 16, 2026111 ms
May 23, 2026100 ms
May 30, 2026100 ms
Jun 6, 202696 ms
Jun 13, 202690 ms
Jun 20, 202696 ms
Jun 27, 202697 ms
Jul 4, 202696 ms
Jul 11, 202694 ms
Jul 18, 202694 ms
Jul 25, 202694 ms
Aug 1, 2026121 ms
Aug 8, 2026162 ms
Aug 15, 2026187 ms
Aug 22, 2026187 ms
Aug 29, 2026107 ms
Sep 5, 2026115 ms
Sep 12, 2026114 ms
Sep 26, 202697 ms
Oct 3, 202689 ms
Oct 10, 202695 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 diapro.it (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. diapro.it at 1.1 s1.1 s
  2. diapro.it at 2.1 s2.1 s
  3. diapro.it at 3.2 s3.2 s
  4. diapro.it at 4.2 s4.2 s
  5. diapro.it at 5.3 s5.3 s
  6. diapro.it at 6.4 s6.4 s
  7. diapro.it at 7.4 s7.4 s
  8. diapro.it at 8.5 s8.5 s

Speed

7 to fix51
  • Render-blocking requests

    3.5 s

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

  • Reduce unused JavaScript

    2.1 s · 394 KiB

    About 394 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

  • Reduce unused CSS

    1.4 s · 224 KiB

    About 224 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 51

    51/100

    Your mobile performance score is 51 (desktop: 51). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    400 ms · 202 KiB

    4 images could be 202 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Font display

    350 ms

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

  • Google CDN adds 127 ms

    127 ms

    Google CDN costs a phone 127 ms of main-thread work and 347 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 (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 652 KiB and 248 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix67
  • 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 LCP: 5.2 s

    5.2 s

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

  • Real-user FCP: 4.9 s

    4.9 s

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

  • Real-user TTFB: 4.0 s

    4.0 s

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

  • Largest Contentful Paint: 14.6 s

    14.6 s

    Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 13.8 s

    13.8 s

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

  • Time to Interactive: 14.6 s

    14.6 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Largest content (LCP) got 29% slower for real visitors

    +29%

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

  • Cumulative Layout Shift: 0.106

    0.106

    The layout shifts by 0.106 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 1 image without width and height

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

4 checks passed
  • Real-user INP: 89 ms

    89 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 23% faster for real visitors

    -23%

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

  • Total Blocking Time: 155 ms

    155 ms

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

Images and page weight

5 to fix25
  • Page weight: 8.8 MB in 80 requests

    8.8 MB

    Your homepage downloads 8.8 MB in 80 requests on a phone: images 7.4 MB (10), scripts 788 KiB (28) and fonts 396 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    S.A.R..png weighs 6.4 MB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (6.5 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

    S.A.R..png 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).

  • 1 image far larger than shown

    109 KiB

    1 image is downloaded at several times the size a phone draws it, for example Diapro_logo.png at 930 px wide, shown at 96 px. Resized copies would save about 109 KiB.

  • About 2.5 g of CO₂ per visit

    2.50 g

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

Accessibility

6 to fixGoogle 8790
  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 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.

  • 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 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7779
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (370 characters)

    Your meta description is 370 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 33 internal links, 0 external

    The homepage links to 33 pages on diapro.it and 0 external pages.

5 checks passed
  • Title: 32 characters

    Your title is a healthy 32 characters: “Dia.Pro Diagnostic Bioprobes srl”.

  • Canonical URL set

    The canonical URL is https://www.diapro.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.diapro.it/sitemap.xml.

AI search readiness

100
4 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 description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.diapro.it/llms.txt (70 KiB, 232 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 6 linked pages hidden from search

    https://www.diapro.it/panel_cat/covid-19, https://www.diapro.it/panel_cat/elisa, https://www.diapro.it/panel_cat/clia, https://www.diapro.it/panel_cat/rt-pcr, https://www.diapro.it/2022/05/13 and https://www.diapro.it/2021/11/30 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.diapro.it/panel_cat/covid-19, https://www.diapro.it/panel_cat/elisa, https://www.diapro.it/panel_cat/clia, https://www.diapro.it/panel_cat/rt-pcr, https://www.diapro.it/2022/05/13 and https://www.diapro.it/2021/11/30 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.diapro.it/the-new-covid-19-variant-omicron-b1-1-529 and https://www.diapro.it/covid-19-disease-the-2020-global-diagnostic-challenge use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://www.diapro.it/about-us, https://www.diapro.it/products-and-technologies, https://www.diapro.it/international-certification, https://www.diapro.it/news, https://www.diapro.it/contact-us and https://www.diapro.it/panel_cat/covid-19 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.diapro.it/the-new-covid-19-variant-omicron-b1-1-529 took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 6 small tap targets

    6 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “$(...).live is not a function”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 325 words of copy

    The homepage carries about 325 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: “LEARN MORE”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact us” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 6 other companies contacted

    Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 diapro.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 © 2021.

Stack

CMS
WordPress
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 43 issues on diapro.it, including 18 speed issues, 5 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

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