Website review, no card needed

isap-packaging.com logo

isap-packaging.com website review

Visit site (opens in a new tab)Reviewed 22 October 202628 issues · 79 checks

This review found 28 issues worth fixing on isap-packaging.com, 10 of them high impact, across 79 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.1 s1.9 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.9 s
May 9, 20262.6 s
May 16, 20262.7 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.6 s
Jun 13, 20262.7 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20262.4 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.4 s
Oct 10, 20262.5 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
122 ms96 msMay 2Oct 17105 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026106 ms
May 9, 2026101 ms
May 16, 2026101 ms
May 23, 202699 ms
May 30, 2026101 ms
Jun 6, 2026101 ms
Jun 13, 2026107 ms
Jun 20, 2026110 ms
Jun 27, 2026107 ms
Jul 4, 2026106 ms
Jul 11, 2026104 ms
Jul 18, 2026104 ms
Jul 25, 2026112 ms
Aug 1, 2026119 ms
Aug 8, 2026116 ms
Aug 15, 2026111 ms
Aug 22, 2026104 ms
Aug 29, 2026106 ms
Sep 5, 2026101 ms
Sep 12, 2026104 ms
Sep 19, 2026110 ms
Sep 26, 2026107 ms
Oct 3, 2026109 ms
Oct 10, 2026108 ms
Oct 17, 2026105 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 isap-packaging.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. isap-packaging.com at 0.8 s0.8 s
  2. isap-packaging.com at 1.7 s1.7 s
  3. isap-packaging.com at 2.5 s2.5 s
  4. isap-packaging.com at 3.3 s3.3 s
  5. isap-packaging.com at 4.1 s4.1 s
  6. isap-packaging.com at 5.0 s5.0 s
  7. isap-packaging.com at 5.8 s5.8 s
  8. isap-packaging.com at 6.6 s6.6 s

Speed

6 to fix61
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 61

    61/100

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

  • Reduce unused CSS

    300 ms · 198 KiB

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

  • Reduce unused JavaScript

    343 KiB

    About 343 KiB of JavaScript is downloaded but never used on this page.

  • iubenda adds 254 ms

    254 ms

    iubenda costs a phone 254 ms of main-thread work and 152 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.

  • FontAwesome CDN adds 0 ms

    0 ms

    FontAwesome CDN costs a phone 0 ms of main-thread work and 556 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (iubenda, Google Tag Manager and Cloudflare CDN and others), adding 945 KiB and 351 ms of main-thread time.

  • Use efficient cache lifetimes

    250 ms · 146 KiB

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

  • Legacy JavaScript

    150 ms · 27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    112 KiB

    2 images could be 112 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 3 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 345 ms

    345 ms

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

Core Web Vitals

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

  • Speed Index: 11.3 s

    11.3 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nata nel 1963, ISAP PACKAGING è specializzata nella produzi…”. Most of its time is element render delay (4.2 s).

  • Time to Interactive: 10.5 s

    10.5 s

    The page becomes fully interactive after 10.5 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: 2.6 s

    2.6 s

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

  • Real-user TTFB: 803 ms

    803 ms

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

  • 3 images without width and height

    3 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-17, real Chrome visitors' tap response (inp) went from 106 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user INP: 104 ms

    104 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 16 ms

    16 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 136 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 136 requests on a phone: scripts 890 KiB (98), fonts 625 KiB (7) and images 429 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.62 g

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

3 checks passed
  • 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

4 to fixGoogle 8793
  • 11 text elements with low contrast

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

  • 9 images without alt text

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

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

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

  • 3 links without text

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

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

1 to fixGoogle 9293
  • Title is short (17 characters)

    Your title is only 17 characters: “ISAP - Gruppo FLO”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 49 internal links, 6 external

    The homepage links to 49 pages on isap-packaging.com and 6 external pages.

7 checks passed
  • Meta description: 104 characters

    Your meta description is 104 characters: “ISAP è l’azienda del gruppo FLO specializzata nella produzione del packaging industriale e dei bicchieri”.

  • One H1 headline

    Your main headline reads: “ISAP”.

  • Canonical URL set

    The canonical URL is https://www.flogroup.eu/gruppo/isap/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.flogroup.eu/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

Other pages

3 to fix83
  • 3 pages share a title

    https://www.flogroup.eu/gruppo/isap, https://www.flogroup.eu/en/group/isap and https://www.flogroup.eu/fr/groupe/isap all use the title “ISAP - Gruppo FLO”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages without a meta description

    https://www.flogroup.eu/en/group/isap, https://www.flogroup.eu/fr/groupe/isap, https://www.flogroup.eu/news, https://www.flogroup.eu/contatti, https://www.flogroup.eu/cataloghi-brochure and https://www.flogroup.eu/informativa-privacy-flo-s-p-a and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    /, https://www.flogroup.eu/en/group/isap, https://www.flogroup.eu/fr/groupe/isap, https://www.flogroup.eu/gruppo, https://www.flogroup.eu/business and https://www.flogroup.eu/prodotti-innovativi and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

  • 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 7791
  • 4 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

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

3 to fix38
  • 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 testimonial or review block. 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 717 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

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

  • 3 cookies set on arrival

    3

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 isap-packaging.com, 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
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 28 issues on isap-packaging.com, including 14 speed issues, 1 SEO issue and 3 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