ptwtrade.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Hotjar and others), adding 1.4 MB and 2.3 s of main-thread time.

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

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

Shopify costs a phone 673 ms of main-thread work and 396 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.

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

Hotjar costs a phone 589 ms of main-thread work and 67 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 415 KiB of JavaScript is downloaded but never used on this page.

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

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

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

14 KiB JavaScript is shipped twice across bundles.

Polyfills for old browsers add 6 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.

3 KiB could be saved by minifying CSS.

The page becomes fully interactive after 18.2 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.

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

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

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

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

Your homepage downloads 3.8 MB in 330 requests on a phone: scripts 1.6 MB (101), other files 928 KiB (132) and images 862 KiB (46). Under 2 MB keeps phones on slow connections fast.

2 images (77 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 1.08 g of CO₂e: 129.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

39 buttons have no accessible name, so screen readers announce just “button”.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Headings should not be empty: 10 elements on the page fail this check, rated minor by axe-core.

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

Your title is 121 characters, so Google will cut it off around 60: “Natural treats for dogs | Pet Treats Wholesale | Trade & Public | UK – Pet Treats Wholesa…”.

There are 14 <h1> headlines (“”, “NEW: Christmas Mega Mix” and “”). One clear main headline is easier for people and search engines.

20 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 348 pages on ptwtrade.com and 6 external pages.

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

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.

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 2,889 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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