wptglobal.com website review

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

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

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

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

Your mobile performance score is 57 (desktop: 85). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.6 MB and 479 ms of main-thread time.

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

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

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

wptglobalkr.com costs a phone 0 ms of main-thread work and 844 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 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Desktop scores 85 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Real visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.64 (75th percentile). Good is under 0.1.

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

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

Your largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “WPT® Global Welcome Package”.

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

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

Real visitors wait 262 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 3.7 MB in 111 requests on a phone: images 2.6 MB (75), scripts 858 KiB (11) and fonts 94 KiB (1). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example non-available-icon.png at 460 px wide, shown at 109 px. Resized copies would save about 254 KiB.

2 images (371 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.

1 image further down the page (84 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 link inside paragraphs relies on colour alone to stand out.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is 70 characters, so Google will cut it off around 60: “WPT Global | Play Poker Online & Casino in the World's Best Poker Site”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 202 pages on wptglobal.com and 19 external pages.

There is no https://wptglobal.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://wptglobal.com/en-ca and https://wptglobal.com/en-my all use the title “WPT Global | Play Poker Online & Casino in the World's Best Poker Site”. Search engines can't tell which page to show for a search, so each competes with the others.

https://wptglobal.com/en-ca and https://wptglobal.com/en-my use the same meta description. A description written for each page earns more clicks.

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

3 images are served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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

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

The homepage carries about 1,485 words of visible text.

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