tonkintaylor.com website review

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

10 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 15.6 s faster on a phone.

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

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

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

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

4 third-party services load with your homepage (Google CDN, cdn-cookieyes.com and Other Google APIs/SDKs and others), adding 4.3 MB and 925 ms of main-thread time.

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

Google CDN costs a phone 691 ms of main-thread work and 734 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.

Other Google APIs/SDKs costs a phone 81 ms of main-thread work and 3.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.

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

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

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

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

2 KiB could be saved by minifying CSS.

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.

Real visitors see the first content after 4.1 s (75th percentile). Good is under 1.8 s.

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

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

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

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

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

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

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

Your homepage downloads 17.8 MB in 167 requests on a phone: images 14.9 MB (30), scripts 1.9 MB (85) and other files 364 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

6 images further down the page (161 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 22 characters: “Home - Tonkin + Taylor”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 5 <h1> headlines (“Together we create and sustain a better world”, “RM Reform” and “Help shape a sustainable future”). One clear main headline is easier for people and search engines.

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

The homepage links to 312 pages on tonkintaylor.com and 20 external pages.

There is no https://www.tonkintaylor.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://www.tonkintaylor.com/nz/sectors, https://www.tonkintaylor.com/nz/sectors/energy, https://www.tonkintaylor.com/nz/sectors/industry, https://www.tonkintaylor.com/nz/sectors/land-buildings, https://www.tonkintaylor.com/nz/markets/pacific-development-resilience and https://www.tonkintaylor.com/nz/sectors/transport and 4 others took over 3 s to send their HTML from our server.

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

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

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

Large scripts ship without source maps.

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

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

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