alpen.com.au website review

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

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

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

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

9 images could be 665 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

5 third-party services load with your homepage (Google Tag Manager, Facebook and Cloudflare and others), adding 313 KiB and 232 ms of main-thread time.

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

29 KiB could be saved by minifying JavaScript.

11 KiB could be saved by minifying CSS.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

Your homepage downloads 3.0 MB in 134 requests on a phone: images 2.1 MB (89), scripts 662 KiB (24) and fonts 87 KiB (3). Under 2 MB keeps phones on slow connections fast.

8 images (866 KiB) 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.

8 images are downloaded at several times the size a phone draws them, for example PD_FoilNumbers_Navy_WebBanner_1300x500px-cr-1300x530.jpg at 1,300 px wide, shown at 360 px. Resized copies would save about 268 KiB.

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

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

1 button has no accessible name, so screen readers announce just “button”.

2 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://alpen.com.au/index.php?route=feed/google_sitemap, so Google discovers your pages only by following links.

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

The homepage links to 1,239 pages on alpen.com.au and 5 external pages.

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.

There is no /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.

/environment, /eco-occasions, /balloons/latex-decrotex-sempertex-balloons, /balloons/latex-decrotex-sempertex-balloons/latex-balloons-decrotex-bulk-prints, /latex-decrotex-sempertex-balloons/latex-balloons-decrotex-bulk-prints/12-cm-latex-balloons and /latex-decrotex-sempertex-balloons/latex-balloons-decrotex-bulk-prints/30-cm-latex-balloons and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/balloons/latex-decrotex-sempertex-balloons/latex-balloons-decrotex-bulk-prints, /latex-decrotex-sempertex-balloons/latex-balloons-decrotex-bulk-prints/12-cm-latex-balloons, /latex-decrotex-sempertex-balloons/latex-balloons-decrotex-bulk-prints/30-cm-latex-balloons, /latex-decrotex-sempertex-balloons/latex-balloons-decrotex-bulk-prints/46cm-all-tones, /latex-decrotex-sempertex-balloons/latex-balloons-decrotex-bulk-prints/60cm-latex and /latex-decrotex-sempertex-balloons/latex-balloons-decrotex-bulk-prints/90cm-latex and 3 others took over 3 s to send their HTML from our server.

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

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

1 image is served at too low a resolution for sharp phone screens.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

alpen.com.au has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

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.

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