yalidine.com website review

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

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

About 407 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.7 s faster on a phone.

About 502 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.

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

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

4 images could be 146 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

16 KiB could be saved by minifying CSS.

Google CDN costs a phone 65 ms of main-thread work and 352 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.

2 KiB could be saved by minifying JavaScript.

4 third-party services load with your homepage (Google CDN, cloudflare.com and Other Google APIs/SDKs and others), adding 515 KiB and 85 ms of main-thread time.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

8 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' tap response (inp) went from 136 ms to 143 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.5 MB in 36 requests on a phone: scripts 711 KiB (9), other files 643 KiB (4) and stylesheets 427 KiB (8). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example delivery-guy-arranging-parcel-3032739-2543537.png at 620 px wide, shown at 198 px. Resized copies would save about 9 KiB.

2 images (208 KiB) 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.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

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

Your meta description is only 41 characters: “Le 1er de la livraison express en Algérie”. 70 to 160 characters is enough to sell the click.

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

No XML sitemap at https://yalidine-express.com.dz/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at yalidine-express.com.dz/robots.txt, the first file search crawlers ask for.

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

The homepage links to 17 pages on yalidine.com and 3 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://yalidine-express.com.dz/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://yalidine-express.com.dz/nos-agences and https://yalidine-express.com.dz/suivre-un-colis all use the title “Le 1er de la livraison express en Algérie”. Search engines can't tell which page to show for a search, so each competes with the others.

https://yalidine-express.com.dz/nos-agences and https://yalidine-express.com.dz/suivre-un-colis use the same meta description. A description written for each page earns more clicks.

https://yalidine-express.com.dz/nos-agences and https://yalidine-express.com.dz/suivre-un-colis have no <h1> headline, so visitors and search engines get no clear main topic.

https://yalidine-express.com.dz/suivre-un-colis 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 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 289 words of visible text.

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