babilgames.com website review

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

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

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

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

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

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

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

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

11 KiB could be saved by minifying JavaScript.

5 KiB could be saved by minifying CSS.

3 third-party services load with your homepage (Clarity, Cloudflare and Google Fonts), adding 49 KiB and 125 ms of main-thread time.

3 long tasks block the main thread while loading, the longest for 72 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).

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.

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

Real visitors see the first content after 5.7 s (75th percentile). Good is under 1.8 s.

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

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

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

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

Real visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

13 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-17, real Chrome visitors' tap response (inp) went from 160 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 8.8 MB in 86 requests on a phone: images 8.0 MB (25), scripts 399 KiB (27) and fonts 323 KiB (4). Under 2 MB keeps phones on slow connections fast.

7 images weigh 7.7 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example Asfet-Alharb.jpg at 1,760 px wide, shown at 350 px. Resized copies would save about 5.0 MB.

7 images (7.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.

8 images further down the page (7.7 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 2.50 g of CO₂e: 300.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 image has no alt text, which hurts accessibility and image search.

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

Your title is only 10 characters: “Babilgames”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 23 pages on babilgames.com and 4 external pages.

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.

/careers and /career all use the title “Careers - Babilgames”. Search engines can't tell which page to show for a search, so each competes with the others.

/montoya_portfolio/nida-harb-3, /montoya_portfolio/tgf, /montoya_portfolio/al-general, /montoya_portfolio/arkan, /montoya_portfolio/baloot-royale and /montoya_portfolio/war-strom and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

/careers and /career use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /career, whose canonical is /careers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/games and /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.

/contact-us took over 3 s to send its HTML from our server.

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

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

Large scripts ship without source maps.

1 link from your homepage to your own site is broken, for example https://babilgames.com/cdn-cgi/content?id=LH1yOiihIilL7kzxO6DhgdWvI_3zAoqkEQ4s80Y4HlA-1792523525.338654-1.2.1.1-DPbnZNQYlRWW6Dm4Zi.d5DjLeW2uOVwxb22hf6d26f1tAWtkn27PBORWXwipMeyf (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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

babilgames.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.

babilgames.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: 11 customer or partner logos. 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 130 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.

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 Microsoft Clarity (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 2 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.