otherside-e.com website review

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

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

Your mobile performance score is 67 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

About 136 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 790 ms faster on a phone.

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

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

6 third-party services load with your homepage (GoDaddy, Google Analytics and trustedsite.com and others), adding 69 KiB and 63 ms of main-thread time.

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

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

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.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ENTER AN IMMERSIVE WORLD OF GAMING WITH US”.

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

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

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

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

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.

OthersideOnSiteOct2022-11-1.png weighs 1.2 MB. 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 OthersideOnSiteOct2022-11-1.png at 1,920 px wide, shown at 142 px. Resized copies would save about 1.5 MB.

Your homepage downloads 2.4 MB in 42 requests on a phone: images 1.9 MB (8), scripts 292 KiB (16) and fonts 101 KiB (3). Under 2 MB keeps phones on slow connections fast.

4 images (1.7 MB) 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.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

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

Your title is 101 characters, so Google will cut it off around 60: “OtherSide Entertainment – Information about OtherSide Entertainment, a video game develop…”.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 23 pages on otherside-e.com and 17 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 https://otherside-e.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.

https://otherside-e.com/our-games, https://otherside-e.com/about, https://otherside-e.com/news, https://otherside-e.com/contact-us, https://otherside-e.com/terms-conditions and https://otherside-e.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://otherside-e.com/our-games, https://otherside-e.com/about, https://otherside-e.com/news and https://otherside-e.com/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://otherside-e.com/our-games and https://otherside-e.com/contact-us 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 6 pages linked from your homepage and read each the way a search engine does.

2 of 9 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.

Social proof on the homepage: 4 trust badges. 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 140 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.

Before a visitor clicks anything, the page loads Google Analytics (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 6 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.