3.9 sec in total
126 ms
2.6 sec
1.2 sec
Welcome to oza.com homepage info - get ready to check Oza best content for Egypt right away, or after learning these important things about oza.com
At OZ Architects, our client's vision is our inspiration and drives each unique design we do. We're here to bring your vision to form.
Visit oza.comWe analyzed Oza.com page load time and found that the first response time was 126 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
oza.com performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value4.1 s
46/100
25%
Value38.4 s
0/100
10%
Value1,010 ms
27/100
30%
Value0
100/100
15%
Value118.7 s
0/100
10%
126 ms
139 ms
245 ms
118 ms
203 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 86% of them (32 requests) were addressed to the original Oza.com, 5% (2 requests) were made to Googletagmanager.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Oza.com.
Page size can be reduced by 278.4 kB (3%)
8.5 MB
8.2 MB
In fact, the total size of Oza.com main page is 8.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 8.1 MB which makes up the majority of the site volume.
Potential reduce by 38.4 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 38.4 kB or 74% of the original size.
Potential reduce by 2.5 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. Oza images are well optimized though.
Potential reduce by 89.1 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 89.1 kB or 51% of the original size.
Potential reduce by 148.4 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. Oza.com needs all CSS files to be minified and compressed as it can save up to 148.4 kB or 63% of the original size.
Number of requests can be reduced by 25 (81%)
31
6
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oza. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
oza.com
126 ms
www.oza.com
139 ms
www.oza.com
245 ms
wp-emoji-release.min.js
118 ms
style.min.css
203 ms
style.css
302 ms
style.css
244 ms
css
58 ms
jquery.min.js
47 ms
jquery-migrate.min.js
128 ms
js
76 ms
style.css
59 ms
style.css
72 ms
style.css
168 ms
lodash.min.js
275 ms
regenerator-runtime.min.js
239 ms
wp-polyfill.min.js
179 ms
react.min.js
203 ms
react-dom.min.js
493 ms
escape-html.min.js
208 ms
element.min.js
231 ms
hooks.min.js
484 ms
i18n.min.js
261 ms
url.min.js
262 ms
api-fetch.min.js
263 ms
scripts.bundle.js
263 ms
public.js
281 ms
public.js
267 ms
Rectangle-1.png
443 ms
Rectangle-3.png
1659 ms
Rectangle-5.png
1341 ms
analytics.js
34 ms
js
60 ms
fa-light-300.woff
332 ms
fa-solid-900.woff
283 ms
fa-brands-400.woff
212 ms
collect
64 ms
oza.com accessibility score
oza.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
oza.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oza.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Oza.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.
oza.com
Open Graph data is detected on the main page of Oza. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: