Mazaya.eg Site Title

Mazaya: Shop Perfumes, Makeup, Skincare in Egypt

Mazaya.eg Meta Description

100% authentic products, biggest beauty retailer in Egypt, 2,000+ products, exclusive brands.

Mazaya.eg Test Results

Mazaya.eg Mobile Performance: 29/100
Quick overview:
Forced reflow
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Layout shift culprits
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Document request latency
Est savings of 1,620 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Time to Interactive
16.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
280 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Use efficient cache lifetimes
Est savings of 193 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Legacy JavaScript
Est savings of 96 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Improve image delivery
Est savings of 188 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce initial server response time
Root document took 1,070 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Minimize main-thread work
3.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid large layout shifts
7 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Avoid an excessive DOM size
1,033 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce unused JavaScript
Est savings of 617 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Avoid serving legacy JavaScript to modern browsers
Est savings of 108 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Reduce JavaScript execution time
1.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Avoid multiple page redirects
Est savings of 1,090 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
6,970 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Reduce unused CSS
Est savings of 18 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Serve static assets with an efficient cache policy
11 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Minify CSS
Est savings of 4 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Properly size images
Est savings of 72 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

Mazaya.eg Mobile SEO: 100/100
Quick overview:

Mazaya.eg Mobile Best Practices: 79/100
Quick overview:
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Mazaya.eg Mobile Accessibility: 71/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[role]`s do not have all required `[aria-*]` attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar sites
Similar tests
www.mazaya.com
www.mazaya.net
www.mazaya.org
www.mazaya.info
www.mazaya.biz
www.mazaya.us
www.mazaya.mobi
www.azaya.eg
www.mazaya.eg
www.nazaya.eg
www.mnazaya.eg
www.nmazaya.eg
www.jazaya.eg
www.mjazaya.eg
www.jmazaya.eg
www.kazaya.eg
www.mkazaya.eg
www.kmazaya.eg
www.mzaya.eg
www.mqzaya.eg
www.maqzaya.eg
www.mqazaya.eg
www.mwzaya.eg
www.mawzaya.eg
www.mwazaya.eg
www.mszaya.eg
www.maszaya.eg
www.msazaya.eg
www.mzzaya.eg
www.mazzaya.eg
www.mzazaya.eg
www.maaya.eg
www.maxaya.eg
www.mazxaya.eg
www.maxzaya.eg
www.masaya.eg
www.mazsaya.eg
www.maaaya.eg
www.mazaaya.eg
www.maazaya.eg
www.mazya.eg
www.mazqya.eg
www.mazaqya.eg
www.mazqaya.eg
www.mazwya.eg
www.mazawya.eg
www.mazwaya.eg
www.mazsya.eg
www.mazasya.eg
www.mazzya.eg
www.mazazya.eg
www.mazaa.eg
www.mazata.eg
www.mazayta.eg
www.mazatya.eg
www.mazaga.eg
www.mazayga.eg
www.mazagya.eg
www.mazaha.eg
www.mazayha.eg
www.mazahya.eg
www.mazaua.eg
www.mazayua.eg
www.mazauya.eg
www.mazay.eg
www.mazayq.eg
www.mazayaq.eg
www.mazayqa.eg
www.mazayw.eg
www.mazayaw.eg
www.mazaywa.eg
www.mazays.eg
www.mazayas.eg
www.mazaysa.eg
www.mazayz.eg
www.mazayaz.eg
www.mazayza.eg
Last Tested: