lvlupgames.ca website review

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

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

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

8 third-party services load with your homepage (Shopify, Google CDN and Amazon Web Services and others), adding 1.7 MB and 515 ms of main-thread time.

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

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

Shopify costs a phone 198 ms of main-thread work and 807 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 2.4 s on main-thread work while loading, 856 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

smile.io costs a phone 71 ms of main-thread work and 458 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.

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

11 KiB could be saved by minifying JavaScript.

1 long task block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LVLUP GAMES CAFE Our board game cafe is open for in-store p…”.

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 320 requests on a phone: scripts 1.6 MB (144), other files 870 KiB (137) and images 501 KiB (11). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example eco-alliance-02.png at 1,323 px wide, shown at 80 px. Resized copies would save about 215 KiB.

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

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

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

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

2 images have no alt text, which hurts accessibility and image search.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 127 pages on lvlupgames.ca and 6 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://lvlupgames.ca/collections/all, https://lvlupgames.ca/collections/blind-bags-boxes, https://lvlupgames.ca/collections/in-stock-games, https://lvlupgames.ca/collections/books and https://lvlupgames.ca/collections/ccg-tcg have no meta description, so Google writes the search snippet from whatever text it finds.

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

19 of 37 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.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 196 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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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