Website review, no card needed

alumil.com logo

alumil.com website review

Visit site (opens in a new tab)Reviewed 17 November 202616 issues · 65 checks

This review found 16 issues worth fixing on alumil.com, 3 of them high impact, across 65 checks. The most urgent: no call to action on the first screen. 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.9 s2.1 sMay 30Nov 143.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.5 s
Aug 22, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.5 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Oct 24, 20263.0 s
Oct 31, 20263.0 s
Nov 7, 20263.0 s
Nov 14, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
267 ms190 msMay 30Nov 14208 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026227 ms
Jun 13, 2026241 ms
Jun 20, 2026239 ms
Jul 4, 2026246 ms
Jul 11, 2026238 ms
Jul 18, 2026242 ms
Jul 25, 2026232 ms
Aug 22, 2026247 ms
Sep 5, 2026258 ms
Sep 12, 2026243 ms
Oct 10, 2026199 ms
Oct 17, 2026203 ms
Oct 24, 2026206 ms
Oct 31, 2026206 ms
Nov 7, 2026210 ms
Nov 14, 2026208 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 alumil.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alumil.com at 0.4 s0.4 s
  2. alumil.com at 0.8 s0.8 s
  3. alumil.com at 1.1 s1.1 s
  4. alumil.com at 1.5 s1.5 s
  5. alumil.com at 1.9 s1.9 s
  6. alumil.com at 2.3 s2.3 s
  7. alumil.com at 2.6 s2.6 s
  8. alumil.com at 3.0 s3.0 s

Speed

3 to fix95
  • Render-blocking requests

    650 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • Reduce unused JavaScript

    300 ms · 239 KiB

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

  • Use efficient cache lifetimes

    300 ms · 77 KiB

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

  • Reduce unused CSS

    150 ms · 157 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Cookiebot and Cloudflare), adding 350 KiB and 188 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.7 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

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

    +29%

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

  • Time to Interactive: 5.1 s

    5.1 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 22 images without width and height

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

11 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

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

    0.00

    For real visitors the layout shifts by 0.00 (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.

  • Real-user TTFB: 592 ms

    592 ms

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • Speed Index: 3.3 s

    3.3 s

    Visually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

  • Total Blocking Time: 69 ms

    69 ms

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

  • Cumulative Layout Shift: 0

    0

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

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: 41.9 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 45 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 45 requests on a phone: scripts 547 KiB (12), fonts 299 KiB (2) and images 260 KiB (24). 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

1 to fixGoogle 9499
  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 1 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 10096
  • No structured data

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

  • No X (Twitter) card tag

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

  • 25 internal links, 1 external

    The homepage links to 25 pages on alumil.com and 1 external page.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Alumil's 35-year experience, 3.200 employees and 18 factories make it one of the major global companies designing and p…”.

  • One H1 headline

    Your main headline reads: “ALUMIL WORLDWIDE”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Alumil, aluminum systems for windows & doors”.

  • Canonical URL set

    The canonical URL is https://www.alumil.com/.

  • 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.alumil.com/greece/sitemap/sitemap-index.xml.

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.alumil.com/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

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 26 small tap targets

    26 of 31 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

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.

  • 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 106 words

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

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

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

  • 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
  • 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 alumil.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
Sitefinity 15.4.8637.0 DX
Analytics
Google Analytics | Google Tag Manager
Hosting
Lancom Ltd.

Company

Founded
1988
Headquarters
Kilkis

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 16 issues on alumil.com, including 7 speed issues, 1 SEO issue 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