Website review, no card needed

campetella.com logo

campetella.com website review

Visit site (opens in a new tab)Reviewed 23 October 202640 issues · 83 checks

This review found 40 issues worth fixing on campetella.com, 16 of them high impact, across 83 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
2.7 s1.6 sMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20261.8 s
Aug 1, 20262.1 s
Aug 8, 20261.9 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20262.3 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
132 ms82 msMay 2Oct 17113 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026104 ms
May 9, 202692 ms
May 16, 202694 ms
May 23, 202688 ms
May 30, 202692 ms
Jun 6, 202698 ms
Jun 13, 2026102 ms
Jun 20, 2026108 ms
Jun 27, 202698 ms
Jul 4, 202699 ms
Jul 11, 202699 ms
Jul 18, 202695 ms
Jul 25, 2026107 ms
Aug 1, 2026108 ms
Aug 8, 2026107 ms
Aug 15, 2026126 ms
Aug 22, 2026111 ms
Aug 29, 2026114 ms
Sep 5, 2026117 ms
Sep 12, 2026109 ms
Sep 19, 2026115 ms
Sep 26, 2026113 ms
Oct 3, 2026116 ms
Oct 10, 2026115 ms
Oct 17, 2026113 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 campetella.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. campetella.com at 0.5 s0.5 s
  2. campetella.com at 1.1 s1.1 s
  3. campetella.com at 1.6 s1.6 s
  4. campetella.com at 2.1 s2.1 s
  5. campetella.com at 2.7 s2.7 s
  6. campetella.com at 3.2 s3.2 s
  7. campetella.com at 3.7 s3.7 s
  8. campetella.com at 4.2 s4.2 s

Speed

8 to fix62
  • Use efficient cache lifetimes

    1.4 s · 2.8 MB

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

  • Reduce unused JavaScript

    1.3 s · 216 KiB

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

  • Font display

    1.1 s

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

  • Improve image delivery

    2.0 MB

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

  • Mobile performance score: 62

    62/100

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

  • Google Tag Manager adds 228 ms

    228 ms

    Google Tag Manager costs a phone 228 ms of main-thread work and 315 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: 2.1 s

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

  • 2,031 HTML elements

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

  • 5 third-party services on the page

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

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    30 KiB

    About 30 KiB of CSS is downloaded but never applied on this page.

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

    186 ms

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

Core Web Vitals

7 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: 6.3 s

    6.3 s

    Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Innovative solutions manufacturers in the field of industri…”.

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Speed Index: 6.7 s

    6.7 s

    Visually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 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.

  • 58 images without width and height

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

  • Time to Interactive: 6.6 s

    6.6 s

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

  • Tap response (INP) got 16% slower for real visitors

    +16%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

6 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 114 ms

    114 ms

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Total Blocking Time: 74 ms

    74 ms

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

  • Cumulative Layout Shift: 0.017

    0.017

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

Images and page weight

5 to fix33
  • 1 image over 500 KB

    NEWS_FAKUMA_2026_2.jpg weighs 1.4 MB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    833 KiB

    4 images are downloaded at several times the size a phone draws them, for example NEWS_FAKUMA_2026_2.jpg at 1,080 px wide, shown at 280 px. Resized copies would save about 833 KiB.

  • Page weight: 3.2 MB in 42 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 42 requests on a phone: images 2.6 MB (21), scripts 566 KiB (9) and fonts 51 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

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

  • 2 images below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.91 g

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

Accessibility

7 to fixGoogle 8290
  • 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.

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 18 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 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 47 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: 47 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

5 to fixGoogle 7581
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Campetella Robotic Center: robots for injection molding automation”.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 7 links crawlers can't follow

    7 links have no real href, so search engines can't follow them.

  • 7 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 110 internal links, 6 external

    The homepage links to 110 pages on campetella.com and 6 external pages.

5 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Campetella Robotic Center is an Italian company specializing in robots design and production for injection molding auto…”.

  • One H1 headline

    Your main headline reads: “Campetella Robotic Center is an Italian company specialized in the production and application of industrial robots and …”.

  • 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://www.campetella.com/sitemap-index.xml.

AI search readiness

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

  • Some text only appears after JavaScript runs

    53%

    The HTML your server sends has 561 of the 1,061 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

100
  • 2 pages slow to respond

    https://www.campetella.com/en/cartesian-side-entry-robots and https://www.campetella.com/en/handling took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    37 of 42 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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.

  • A 8-field form

    Your longest form asks for 8 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 1,061 words of copy

    The homepage carries about 1,061 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

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

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 campetella.com, 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 © 2024.

Stack

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 40 issues on campetella.com, including 15 speed issues, 5 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