nazih.com website review

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

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

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

YouTube costs a phone 2.5 s of main-thread work and 3.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Your mobile performance score is 18. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

About 2.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

40 KiB could be saved by minifying CSS.

The page has 1,568 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

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.

5 KiB could be saved by minifying JavaScript.

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.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.32 (75th percentile). Good is under 0.1.

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

Your largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nazih”.

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

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

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

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

The layout shifts by 0.3 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

31 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 131 ms to 156 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.6 MB in 170 requests on a phone: images 7.1 MB (84), scripts 4.3 MB (32) and stylesheets 499 KiB (13). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

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

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

9 images are downloaded at several times the size a phone draws them, for example nazih_banner_2021.jpg at 1,200 px wide, shown at 360 px. Resized copies would save about 347 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 3.56 g of CO₂e: 427.6 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”.

1 dropdown has no label.

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

4 frames have no title, so screen-reader users cannot tell what they contain.

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

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption. (1 element).

<td> elements in a large <table> do not have table headers. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

Your meta description is only 43 characters: “Discover the wide range of Beauty products.”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 326 pages on nazih.com and 28 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://nazih.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://nazih.com/beautyblog and https://nazih.com/live have no meta description, so Google writes the search snippet from whatever text it finds.

https://nazih.com/live has no <h1> headline, so visitors and search engines get no clear main topic.

https://nazih.com/live 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 199 found) 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.

5 images are served at too low a resolution for sharp phone screens.

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

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 8 fields (5 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and X (Twitter) Ads (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 10 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.