yalla.online website review

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

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

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

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

26 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, YouTube and Facebook and others), adding 2.7 MB and 1.1 s of main-thread time.

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

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

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

79 KiB could be saved by minifying JavaScript.

YouTube costs a phone 327 ms of main-thread work and 972 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.

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

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

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

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 58.1 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 17.7 s (Speed Index). Good is under 3.4 s.

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

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

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

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

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

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

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

Your homepage downloads 11.7 MB in 149 requests on a phone: other files 3.4 MB (15), images 2.8 MB (99) and scripts 2.7 MB (25). Under 2 MB keeps phones on slow connections fast.

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

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

4 images are downloaded at several times the size a phone draws them, for example yalla-super-app-11.png at 375 px wide, shown at 70 px. Resized copies would save about 263 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

24 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 113 characters, so Google will cut it off around 60: “Yalla Prepaid Card & Super App - Send, Spend, Receive, Save, Invest Money and Order all y…”.

There are 23 <h1> headlines (“Become a Partner”, “Get Yalla Card” and “Share Website”). One clear main headline is easier for people and search engines.

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:title and og:description, so shared links fall back to guesses.

The homepage links to 23 pages on yalla.online and 10 external pages.

There is no https://yalla.online/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://yalla.online/ar/index.html declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://yalla.online/yalla-for-business.html, https://yalla.online/storelocator.html, https://yalla.online/press.html, https://yalla.online/privacy-policy.html and https://yalla.online/terms-of-use.html all use the title “Yalla Super App Egypt, Online Grocery Payment Gateway Egypt”. Search engines can't tell which page to show for a search, so each competes with the others.

https://yalla.online/download, https://yalla.online/Careers/yalla-make-money, https://yalla.online/Careers/yalla-academy and https://yalla.online/Careers have no meta description, so Google writes the search snippet from whatever text it finds.

https://yalla.online/yalla-for-business.html, https://yalla.online/storelocator.html, https://yalla.online/press.html, https://yalla.online/privacy-policy.html and https://yalla.online/terms-of-use.html use the same meta description. A description written for each page earns more clicks.

https://yalla.online/download, https://yalla.online/Careers/yalla-make-money, https://yalla.online/Careers/yalla-academy and https://yalla.online/Careers have no <h1> headline, so visitors and search engines get no clear main topic.

https://yalla.online/ar/index.html, https://yalla.online/Careers/yalla-make-money, https://yalla.online/Careers/yalla-academy and https://yalla.online/Careers 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 10 pages linked from your homepage and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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: “2.7M Users”. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 11 fields (0 required). Every extra field lowers completion.

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.

The homepage carries about 606 words of visible text.

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 9 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.