Website review, no card needed

fibrenet.it logo

fibrenet.it website review

Visit site (opens in a new tab)Reviewed 3 November 202642 issues · 89 checks

This review found 42 issues worth fixing on fibrenet.it, 20 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
4.5 s2.4 sMay 16Oct 313.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20263.1 s
Jul 11, 20263.4 s
Jul 18, 20263.4 s
Jul 25, 20263.6 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20264.0 s
Aug 22, 20264.1 s
Aug 29, 20264.3 s
Sep 5, 20263.9 s
Sep 12, 20263.6 s
Sep 19, 20263.6 s
Sep 26, 20263.6 s
Oct 3, 20263.6 s
Oct 10, 20263.8 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Oct 31, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
117 ms92 msMay 16Oct 3197 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202696 ms
May 23, 202695 ms
May 30, 202696 ms
Jun 6, 2026101 ms
Jun 13, 2026106 ms
Jun 20, 2026107 ms
Jun 27, 2026107 ms
Jul 4, 2026101 ms
Jul 11, 202698 ms
Jul 18, 202697 ms
Jul 25, 202697 ms
Aug 1, 2026100 ms
Aug 8, 202699 ms
Aug 15, 2026102 ms
Aug 22, 202699 ms
Aug 29, 2026102 ms
Sep 5, 2026102 ms
Sep 12, 2026105 ms
Sep 19, 2026114 ms
Sep 26, 2026107 ms
Oct 3, 2026106 ms
Oct 10, 2026106 ms
Oct 17, 2026102 ms
Oct 24, 202696 ms
Oct 31, 202697 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 fibrenet.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fibrenet.it at 1.4 s1.4 s
  2. fibrenet.it at 2.7 s2.7 s
  3. fibrenet.it at 4.1 s4.1 s
  4. fibrenet.it at 5.4 s5.4 s
  5. fibrenet.it at 6.8 s6.8 s
  6. fibrenet.it at 8.1 s8.1 s
  7. fibrenet.it at 9.5 s9.5 s
  8. fibrenet.it at 10.8 s10.8 s

Speed

10 to fix45
  • Use efficient cache lifetimes

    1.5 s · 5.9 MB

    72 files are served with short cache lifetimes, so returning visitors download them again (5.9 MB).

  • Reduce unused JavaScript

    2.4 s · 767 KiB

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

  • Render-blocking requests

    3.1 s

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

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    3.3 MB

    6 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and iubenda and others), adding 1.7 MB and 1.5 s of main-thread time.

  • Google CDN adds 609 ms

    609 ms

    Google CDN costs a phone 609 ms of main-thread work and 772 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 Tag Manager adds 521 ms

    521 ms

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

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Minify JavaScript

    300 ms · 47 KiB

    47 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 132 KiB

    About 132 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.

  • 16 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    11 KiB

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

  • Minify CSS

    9 KiB

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

  • 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: 115 ms

    115 ms

    Your server sent the HTML in 115 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 FCP: 3.6 s

    3.6 s

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

  • Real-user TTFB: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 11.2 s

    11.2 s

    Your largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (8.8 s).

  • Speed Index: 19.0 s

    19.0 s

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

  • Time to Interactive: 28.7 s

    28.7 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

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

    +29%

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

  • Total Blocking Time: 524 ms

    524 ms

    Scripts block taps and scrolling for 524 ms in total while the page loads. Good is under 200 ms.

  • 12 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

3 checks passed
  • Real-user INP: 92 ms

    92 ms

    Real visitors wait 92 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.

  • Cumulative Layout Shift: 0.049

    0.049

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

Images and page weight

5 to fix18
  • Page weight: 8.1 MB in 109 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 109 requests on a phone: images 5.5 MB (34), scripts 1.8 MB (38) and other files 368 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    2.0 MB

    2 images are downloaded at several times the size a phone draws them, for example img_sec_prodotti.jpg at 2,657 px wide, shown at 360 px. Resized copies would save about 2.0 MB.

  • 4 images in older formats

    4 images (3.6 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.

  • 3 images below the first screen load straight away

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

  • About 2.3 g of CO₂ per visit

    2.28 g

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

Accessibility

8 to fixGoogle 8089
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 4 tap targets too small

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

  • Links look like plain text

    3 links inside paragraphs rely on colour alone to stand out.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • All page content should be contained by landmarks (15 elements)

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

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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

2 to fixGoogle 8593
  • Meta description is long (167 characters)

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

  • 16 links crawlers can't follow

    16 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 set, so this is minor.

  • 122 internal links, 8 external

    The homepage links to 122 pages on fibrenet.it and 8 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Soluzioni tecniche per l’edilizia e le infrastrutture”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “FIBRE NET | Specialisti del rinforzo strutturale”.

  • Canonical URL set

    The canonical URL is https://fibrenet.it/.

  • Structured data in place

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

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

AI search readiness

100
  • No llms.txt

    There is no https://fibrenet.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 (798 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 10 pages without a meta description

    https://fibrenet.it/prodotti, https://fibrenet.it/sistemi/crm, https://fibrenet.it/sistemi/frcm, https://fibrenet.it/sistemi/frp, https://fibrenet.it/sistemi/ristilatura-armata and https://fibrenet.it/sistemi/antisfondellamento and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://fibrenet.it/prodotti, https://fibrenet.it/sistemi/crm, https://fibrenet.it/sistemi/frcm, https://fibrenet.it/sistemi/frp, https://fibrenet.it/sistemi/ristilatura-armata and https://fibrenet.it/sistemi/antisfondellamento and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages slow to respond

    https://fibrenet.it/sistemi/crm, https://fibrenet.it/sistemi/frcm, https://fibrenet.it/sistemi/frp, https://fibrenet.it/sistemi/ristilatura-armata, https://fibrenet.it/sistemi/antisfondellamento and https://fibrenet.it/sistemi/dispositivi-antisismici and 4 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 42 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • 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

2 to fixGoogle 9687
  • 13 small tap targets

    13 of 30 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

2 to fix70
  • 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.

  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 496 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Documenti e Download”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before 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 (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (measured from a US location before any click).

  • 16 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
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 42 issues on fibrenet.it, including 21 speed issues, 2 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