highmoonstudios.com website review

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, Optanon and Google CDN and others), adding 920 KiB and 509 ms of main-thread time.

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

About 351 KiB of JavaScript is downloaded but never used on this page.

30 KiB could be saved by minifying JavaScript.

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

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

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

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

Your largest element takes 49.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “For 23 years, we've been crafting games and forging lasting…”.

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

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

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

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

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

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

Your homepage downloads 10.3 MB in 54 requests on a phone: images 9.3 MB (12), scripts 928 KiB (14) and fonts 71 KiB (2). Under 2 MB keeps phones on slow connections fast.

3 images weigh 9.1 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example cod20_reveal_09.png at 6,144 px wide, shown at 390 px. Resized copies would save about 8.5 MB.

2 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (654 KiB) is 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 2.93 g of CO₂e: 352.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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

Your title is only 17 characters: “High Moon Studios”. Between 30 and 65 characters leaves room to say what you do and for whom.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.highmoonstudios.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at highmoonstudios.com/robots.txt, the first file search crawlers ask for.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 8 pages on highmoonstudios.com and 15 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.

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

/the-people and /games have no meta description, so Google writes the search snippet from whatever text it finds.

/the-people and /games have no <h1> headline, so visitors and search engines get no clear main topic.

/games has 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 2 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

http://highmoonstudios.com does not redirect to https, so some visitors land on the insecure version.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

highmoonstudios.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

highmoonstudios.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

highmoonstudios.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 10 cookies (measured from a US location before any click).

Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.