Website review, no card needed

bccsi.it logo

bccsi.it website review

Visit site (opens in a new tab)Reviewed 29 October 202640 issues · 81 checks

This review found 40 issues worth fixing on bccsi.it, 14 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
2.5 s1.8 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.0 s
May 23, 20261.9 s
May 30, 20262.0 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.2 s
Aug 22, 20262.1 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
118 ms73 msMay 9Oct 2498 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202689 ms
May 16, 202692 ms
May 23, 202685 ms
May 30, 202678 ms
Jun 6, 202685 ms
Jun 13, 202684 ms
Jun 20, 202692 ms
Jun 27, 202695 ms
Jul 4, 2026104 ms
Jul 11, 2026111 ms
Jul 18, 202696 ms
Jul 25, 202694 ms
Aug 1, 202694 ms
Aug 8, 202694 ms
Aug 15, 202694 ms
Aug 22, 202694 ms
Sep 12, 2026113 ms
Sep 19, 2026113 ms
Sep 26, 202695 ms
Oct 3, 202695 ms
Oct 10, 202690 ms
Oct 17, 202689 ms
Oct 24, 202698 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 bccsi.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bccsi.it at 0.5 s0.5 s
  2. bccsi.it at 1.1 s1.1 s
  3. bccsi.it at 1.6 s1.6 s
  4. bccsi.it at 2.1 s2.1 s
  5. bccsi.it at 2.7 s2.7 s
  6. bccsi.it at 3.2 s3.2 s
  7. bccsi.it at 3.8 s3.8 s
  8. bccsi.it at 4.3 s4.3 s

Speed

8 to fix41
  • Reduce unused JavaScript

    2.4 s · 403 KiB

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

  • Use efficient cache lifetimes

    1.6 s · 384 KiB

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

  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 41

    41/100

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

  • Reduce unused CSS

    450 ms · 82 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Maps, Accessibe Accessibility Overlay and bcc.it), adding 1.2 MB and 256 ms of main-thread time.

  • Google Maps adds 101 ms

    101 ms

    Google Maps costs a phone 101 ms of main-thread work and 394 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.

  • bcc.it adds 70 ms

    70 ms

    bcc.it costs a phone 70 ms of main-thread work and 583 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.

  • Minify CSS

    150 ms · 16 KiB

    16 KiB could be saved by minifying CSS.

  • 2 long tasks on the main thread

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

  • Improve image delivery

    6 KiB

    1 image could be 6 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

9 to fix100
  • 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: 9.3 s

    9.3 s

    Your largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BCC Sistemi Informatici Banner Hero”.

  • Cumulative Layout Shift: 0.848

    0.848

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

  • Time to Interactive: 9.3 s

    9.3 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 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

    +3%

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

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

    +15%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 96 ms

    96 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Total Blocking Time: 122 ms

    122 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.35 g

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

4 checks passed
  • Page weight: 1.2 MB in 51 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 51 requests on a phone: scripts 834 KiB (19), images 223 KiB (14) and stylesheets 113 KiB (7). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 9692
  • Malformed lists

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

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

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

6 to fixGoogle 9267
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (23 characters)

    Your title is only 23 characters: “BCC Sistemi Informatici”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“BCC Sistemi Informatici” and “Offerta”). 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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 43 internal links, 4 external

    The homepage links to 43 pages on bccsi.it and 4 external pages.

2 checks passed
  • 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.bccsi.it/sitemap.asp.

AI search readiness

1 to fix83
  • 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.bccsi.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.

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

Other pages

2 to fix88
  • 8 pages share a title

    /, https://www.bccsi.it/system/bannerTrans.asp, https://www.bccsi.it/page/default.asp, https://www.bccsi.it/doc2/default.asp, https://www.bccsi.it/template/default.asp and https://www.bccsi.it/contents/default.asp and 2 others all use the title “BCC Sistemi Informatici”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://www.bccsi.it/system/bannerTrans.asp, https://www.bccsi.it/page/default.asp, https://www.bccsi.it/doc2/default.asp, https://www.bccsi.it/template/default.asp, https://www.bccsi.it/contents/default.asp and https://www.bccsi.it/privacy.asp and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages with very little text

    https://www.bccsi.it/template/default.asp and https://www.bccsi.it/contents/default.asp have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 7 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 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 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 8 small tap targets

    8 of 23 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

6 to fix36
  • 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.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 126 words

    The homepage has only about 126 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • 2 short forms

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

Privacy and tracking

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

  • 4 other companies contacted

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

1 checks passed
  • 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 bccsi.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 © 2010.

Stack

Framework
jQuery
Hosting
Imperva

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on bccsi.it, including 17 speed issues, 6 SEO issues and 6 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