Website review, no card needed

asco.be logo

asco.be website review

Visit site (opens in a new tab)Reviewed 18 November 202615 issues · 27 checks

This review found 15 issues worth fixing on asco.be, 5 of them high impact, across 27 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

Site score

62D

Not ranked: the homepage didn't load normally in this review.

One score from every part of this review. How it works

Full-page screenshot of asco.be (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. asco.be at 1.8 s1.8 s
  2. asco.be at 3.6 s3.6 s
  3. asco.be at 5.4 s5.4 s
  4. asco.be at 7.2 s7.2 s
  5. asco.be at 9.0 s9.0 s
  6. asco.be at 10.8 s10.8 s
  7. asco.be at 12.6 s12.6 s
  8. asco.be at 14.4 s14.4 s

Speed

6 to fix67
  • Render-blocking requests

    1.2 s

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

  • Use efficient cache lifetimes

    750 ms · 1.3 MB

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

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • Font display

    800 ms

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

  • Improve image delivery

    365 KiB

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

  • Reduce unused CSS

    300 ms · 61 KiB

    About 61 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

    180 ms · 43 KiB

    About 43 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 180 ms faster on a phone.

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

2 checks passed
  • Main-thread work: 0.4 s

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

  • Server response: 99 ms

    99 ms

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

Core Web Vitals

4 to fix72
  • Speed Index: 20.5 s

    20.5 s

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

  • Cumulative Layout Shift: 0.413

    0.413

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 5 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “ASCO INDUSTRIES: A POWERHOUSE FOR AEROSPACE STRUCTURAL PARTS”.

  • Time to Interactive: 2.3 s

    2.3 s

    The page is fully interactive after 2.3 s.

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.38 g

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

1 checks passed
  • Page weight: 1.4 MB in 38 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 38 requests on a phone: fonts 699 KiB (2), images 411 KiB (7) and scripts 169 KiB (17). That is a lean page.

Accessibility

2 to fix89
  • Image elements do not have [alt] attributes

    Image elements do not have [alt] attributes (1 element).

  • <html> element does not have a [lang] attribute

    <html> element does not have a [lang] attribute (1 element).

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

SEO

2 to fixGoogle 7750
  • 1 link crawlers can't follow

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

  • robots.txt is invalid

    robots.txt has 1 error.

Best practices

Google 100

Not measured in this review.

Content and conversion

1 to fix0
  • Homepage could not be loaded

    We could not load https://asco.be from our server, so the homepage checks are missing. If the site is up, it may block automated visitors.

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 asco.be, 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
Hosting
Cogent Communications, LLC

Company

Founded
1954
Headquarters
Zaventem

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 15 issues on asco.be, including 10 speed issues, 2 SEO issues and 1 conversion gap. 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