myprize.us website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 875 KiB and 985 ms of main-thread time.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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

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

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

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

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 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Your largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Previous Next REFER JOIN JOIN JOIN”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.0 MB in 394 requests on a phone: scripts 2.5 MB (212), images 1.6 MB (64) and HTML 623 KiB (2). Under 2 MB keeps phones on slow connections fast.

Njg5MWZlMjMtZTRmYi00NWYwLThhNWYtYWU0MTc2NmQzYTkx 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).

5 images are downloaded at several times the size a phone draws them, for example jackpotfantasy-N2U1YzhmYzMtNjM4Yi00YmRjLTliOTEtMzE3NzVhODc3O at 800 px wide, shown at 56 px. Resized copies would save about 236 KiB.

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

Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

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

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

The homepage links to 15 pages on myprize.us and 1 external page.

There is no https://myprize.us/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://myprize.us/leaderboard/4a303633-1938-4edf-a1df-c7c9ff8c8097, https://myprize.us/leaderboard/594d4120-c9f1-456b-8db2-324433049b01, https://myprize.us/explore/games/playson and https://myprize.us/packs all use the title “MyPrize US - Play Together with creators and friends”. Search engines can't tell which page to show for a search, so each competes with the others.

https://myprize.us/leaderboard/4a303633-1938-4edf-a1df-c7c9ff8c8097, https://myprize.us/leaderboard/594d4120-c9f1-456b-8db2-324433049b01, https://myprize.us/explore/games/playson and https://myprize.us/packs use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://myprize.us/explore/games/playson, whose canonical is https://myprize.us/explore/games. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Waiting for user for API calls TIMED OUT!!!”.

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

Large scripts ship without source maps.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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 116 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 Amplitude, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 mores (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 23 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.