ourgamesph.com website review

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

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

13 images could be 401 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.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

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

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

1 third-party service load with your homepage (Shopify), adding 393 KiB and 146 ms of main-thread time.

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

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 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.9 MB in 331 requests on a phone: other files 1.2 MB (218), images 1.0 MB (33) and scripts 486 KiB (48). Under 2 MB keeps phones on slow connections fast.

TCG_Fiesta.png 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).

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

6 images (646 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 is downloaded at several times the size a phone draws it, for example TCG_Fiesta.png at 1,369 px wide, shown at 390 px. Resized copies would save about 71 KiB.

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

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

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

Your title is only 21 characters: “Our Games Philippines”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 119 pages on ourgamesph.com and 4 external pages.

There is no https://ourgamesph.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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ourgamesph.com/products/magic-the-gathering%C2%AE-the-hobbit%E1%B5%80%E1%B4%B9-play-booster-30-display, whose canonical is https://ourgamesph.com/products/magic-the-gathering%c2%ae-the-hobbit%e1%b5%80%e1%b4%b9-play-booster-30-display. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 788 words of visible text.

Opening the homepage sets 5 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.