royaloaks.com website review

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

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

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

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

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

8 third-party services load with your homepage (formstack.com, talkfurther.com and Google Tag Manager and others), adding 5.3 MB and 1.8 s of main-thread time.

9 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

formstack.com costs a phone 988 ms of main-thread work and 1.4 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.

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

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

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

website-files.com costs a phone 94 ms of main-thread work and 2.9 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.

talkfurther.com costs a phone 193 ms of main-thread work and 436 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.

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

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

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

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

Your largest element takes 36.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “When Was The Last Time You Worried About — Nothing at All?”.

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

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

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

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

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

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

Your homepage downloads 8.7 MB in 226 requests on a phone: scripts 2.9 MB (50), fonts 2.7 MB (79) and images 2.7 MB (29). Under 2 MB keeps phones on slow connections fast.

680a65832a0910dfce902e66_ROAK-homehero-1920x775-p-500.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

6 images (588 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.

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

1 dropdown has no label.

Form elements should have a visible label: 5 elements on the page fail this check, rated serious by axe-core.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 15 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.

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

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

Structured data found (LocalBusiness and Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 62 pages on royaloaks.com and 8 external pages.

https://www.royaloaks.com/our-team and https://www.royaloaks.com/aventur-team use the same meta description. A description written for each page earns more clicks.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355027879&Ver=2&mid=8213a325-e8cb-48f1-b481-3d14bb971634&bo=1&sid=453f6710d3dc11f1bbf033a1fb04a152&vid=453f8840d3dc11f187fd591bbe4ce8cc&vids=1&msclkid=N&pi=918639831&l.

9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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 22 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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.