3 sec in total
504 ms
2.2 sec
267 ms
Click here to check amazing Ezozo content for Egypt. Otherwise, check out these important facts you probably never knew about ezozo.com
إى زوزو دوت كم اسهل اسرع ارخص تسوق عبر الانترنت سوق منتجاتك من خلال صفحتك واعلاناتك أكبر التسجيل وإعلانات النشر مجانيةسوق دولى على الإنترنت للبيع جملة - تجارى - قطاعى
Visit ezozo.comWe analyzed Ezozo.com page load time and found that the first response time was 504 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
ezozo.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value10.3 s
0/100
25%
Value7.3 s
29/100
10%
Value1,360 ms
17/100
30%
Value0.457
19/100
15%
Value10.3 s
25/100
10%
504 ms
203 ms
166 ms
250 ms
239 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 60% of them (36 requests) were addressed to the original Ezozo.com, 17% (10 requests) were made to Static.xx.fbcdn.net and 13% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (504 ms) belongs to the original domain Ezozo.com.
Page size can be reduced by 181.8 kB (45%)
403.6 kB
221.8 kB
In fact, the total size of Ezozo.com main page is 403.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 188.7 kB which makes up the majority of the site volume.
Potential reduce by 49.3 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 49.3 kB or 82% of the original size.
Potential reduce by 23.2 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Ezozo needs image optimization as it can save up to 23.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 87.2 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 87.2 kB or 68% of the original size.
Potential reduce by 22.1 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Ezozo.com needs all CSS files to be minified and compressed as it can save up to 22.1 kB or 84% of the original size.
Number of requests can be reduced by 24 (41%)
59
35
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ezozo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
ezozo.com
504 ms
style.css
203 ms
fb_likebox.js
166 ms
jquery.min.js
250 ms
jquery.js
239 ms
mootools-yui-compressed.js
130 ms
egypt.gif
129 ms
register.png
129 ms
login.png
130 ms
4.jpg
130 ms
1_13652.jpg
131 ms
1_13651.jpg
237 ms
1_13644.jpg
131 ms
nophoto.png
190 ms
1_13633.jpg
186 ms
1_13631.jpg
186 ms
1_13630.jpg
187 ms
1_13627.png
187 ms
1_13626.jpg
191 ms
1_13621.jpg
190 ms
1_13608.jpg
191 ms
building_w.png
192 ms
building.png
230 ms
car_w.png
230 ms
car.png
231 ms
job_w.png
230 ms
job.png
231 ms
mobile_w.png
264 ms
mobile.png
266 ms
ads_w.png
266 ms
ads.png
266 ms
rss.png
266 ms
home.png
230 ms
arrow.png
246 ms
add.png
266 ms
search.png
264 ms
fb_likebox.png
93 ms
widgets.js
7 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
29 ms
follow_button.6a78875565a912489e9aef879c881358.ar.html
15 ms
likebox.php
362 ms
jot
95 ms
xYm_UD1pmAz.css
172 ms
TGpOWuX6Pv8.css
212 ms
_rx8naC75Dy.js
300 ms
x5F9OMjKyLw.js
377 ms
ICDbTSzjQEg.js
324 ms
TTCre3391I0.js
322 ms
10513295_498399326959456_6401782684359620422_n.jpg
261 ms
1236004_360782314054492_1910326489_n.jpg
357 ms
10154481_289636627868670_4830784848967864186_n.jpg
379 ms
12541079_1036519139704446_5680043038886344455_n.jpg
415 ms
1379841_10150004552801901_469209496895221757_n.jpg
381 ms
12508879_1519037521758038_2368338922289495630_n.jpg
381 ms
11059768_10206440814555449_277919687351513960_n.jpg
460 ms
12191615_894207550664906_364211859536264943_n.jpg
436 ms
wL6VQj7Ab77.png
68 ms
s7jcwEQH7Sx.png
67 ms
I6-MnjEovm5.js
41 ms
vlXaquuXMrr.js
44 ms
ezozo.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
ezozo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ezozo.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
AR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezozo.com can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ezozo.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
ezozo.com
Open Graph description is not detected on the main page of Ezozo. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: