thearcadeguys.com website review

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

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

8 third-party services load with your homepage (heatmap.com, Hotjar and Google Tag Manager and others), adding 2.1 MB and 1.1 s of main-thread time.

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

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

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

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

Google Tag Manager costs a phone 158 ms of main-thread work and 308 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 136 ms of main-thread work and 380 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.

cloudfront.net costs a phone 108 ms of main-thread work and 388 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.

tidio.co costs a phone 85 ms of main-thread work and 515 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.

32 KiB could be saved by minifying JavaScript.

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

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

5 images could be 81 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

11 KiB JavaScript is shipped twice across bundles.

8 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

Your homepage downloads 4.3 MB in 263 requests on a phone: scripts 2.7 MB (68), other files 743 KiB (149) and images 462 KiB (26). Under 2 MB keeps phones on slow connections fast.

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 15 characters: “The Arcade Guys”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 30 pages on thearcadeguys.com 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://thearcadeguys.com/products/tag-ultimate-retro-55-tv, https://thearcadeguys.com/products/build-your-own-55-retro-plus-arcade and https://thearcadeguys.com/products/tag-ultimate-retro-arcade-32-tv all use the title “Retro Arcade Machine – The Arcade Guys”. Search engines can't tell which page to show for a search, so each competes with the others.

https://thearcadeguys.com/collections/our-arcade-collection, https://thearcadeguys.com/collections/custom-arcades, https://thearcadeguys.com/pages/our-reviews-1, https://thearcadeguys.com/policies/terms-of-service, https://thearcadeguys.com/policies/privacy-policy and https://thearcadeguys.com/policies/refund-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://thearcadeguys.com/pages/contact-us and https://thearcadeguys.com/pages/support have no <h1> headline, so visitors and search engines get no clear main topic.

https://thearcadeguys.com/pages/our-reviews-1 and https://thearcadeguys.com/pages/wraps-gallery have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://thearcadeguys.com/.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

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

The homepage carries about 389 words of visible text.

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