mtruapehu.com website review

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

1 image could be 487 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

About 233 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

Your mobile performance score is 40 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Amazon Web Services and others), adding 2.0 MB and 1.3 s of main-thread time.

Google Tag Manager costs a phone 846 ms of main-thread work and 356 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.

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

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

Facebook costs a phone 395 ms of main-thread work and 279 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.

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

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

whakapapa.com costs a phone 3 ms of main-thread work and 1.3 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.

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

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

6 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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.

mtruapehu_portrait_426e67eb88.jpg weighs 581 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.1 MB in 30 requests on a phone: images 1.3 MB (10), scripts 694 KiB (6) and fonts 55 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image (581 KiB) is 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.

1 image is downloaded at several times the size a phone draws it, for example mtruapehu_portrait_426e67eb88.jpg at 1,800 px wide, shown at 390 px. Resized copies would save about 336 KiB.

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

Page should contain a level-one heading: 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.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 10 characters: “Mt Ruapehu”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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://mtruapehu.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at mtruapehu.com/robots.txt, the first file search crawlers ask for.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

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 https://mtruapehu.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.

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

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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

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

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

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 4 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.