alpnrock.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Facebook and rebuyengine.com and others), adding 7.2 MB and 1.1 s of main-thread time.

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

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

Shopify costs a phone 274 ms of main-thread work and 5.6 MB 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.

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

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

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

rebuyengine.com costs a phone 165 ms of main-thread work and 711 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.

Klaviyo costs a phone 126 ms of main-thread work and 345 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.

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

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

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

21 KiB could be saved by minifying JavaScript.

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 page becomes fully interactive after 26.1 s. Good is under 3.8 s.

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

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cozy Up | Alp N Rock”.

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

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

Scripts block taps and scrolling for 276 ms in total while the page loads. Good is under 200 ms.

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

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

Your homepage downloads 10.9 MB in 380 requests on a phone: media 6.1 MB (1), scripts 2.1 MB (119) and images 1.1 MB (46). Under 2 MB keeps phones on slow connections fast.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

Elements with visible text labels do not have matching accessible names. (2 elements).

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

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

The homepage links to 149 pages on alpnrock.com and 3 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

https://alpnrock.com/a/ps/landing_pages/983157/landing-page-cd09e2 has no meta description, so Google writes the search snippet from whatever text it finds.

https://alpnrock.com/a/ps/landing_pages/983157/landing-page-cd09e2 has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 54 fields (0 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 814 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads and 3 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 40 cookies, 1 of them by other companies (measured from a US location before any click).

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