ziyad.com website review

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

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

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

6 images could be 583 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.

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

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

Polyfills for old browsers add 65 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.0 s on main-thread work while loading, 943 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 798 KiB and 447 ms of main-thread time.

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

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 see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 25.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Authentic Middle Eastern Foods Your family will love Plan y…”.

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

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

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

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

1 image 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' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.6 MB in 35 requests on a phone: scripts 1.8 MB (13), stylesheets 1.0 MB (4) and images 1.0 MB (8). Under 2 MB keeps phones on slow connections fast.

4 images (206 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 1.30 g of CO₂e: 155.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

3 links inside paragraphs rely on colour alone to stand out.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

The homepage links to 75 pages on ziyad.com and 8 external pages.

There is no https://www.ziyad.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://www.ziyad.com/author/mevato and https://www.ziyad.com/author/dmikbelgmfoods-com declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://www.ziyad.com/author/mevato and https://www.ziyad.com/author/dmikbelgmfoods-com all use the title “Ziyad - Authentic foods - Your family will love”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ziyad.com/author/mevato and https://www.ziyad.com/author/dmikbelgmfoods-com use the same meta description. A description written for each page earns more clicks.

https://www.ziyad.com/recipe/tahini-grape-molasses-squares has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ziyad.com/careers 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 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://www.ziyad.com/.

1 error was logged to the browser console while the page loaded, for example “gform.addAction is not a function”.

1 image is served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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