4.6 sec in total
160 ms
3.4 sec
957 ms
Visit ozias.co now to see the best up-to-date Ozias content for India and also check out these interesting facts you probably never knew about ozias.co
We help B2B companies increase leads from Google, Facebook, LinkedIn. We're known for our transparency!
Visit ozias.coWe analyzed Ozias.co page load time and found that the first response time was 160 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ozias.co performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value4.1 s
47/100
25%
Value4.2 s
77/100
10%
Value160 ms
93/100
30%
Value0.029
100/100
15%
Value5.3 s
73/100
10%
160 ms
443 ms
288 ms
332 ms
27 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 89% of them (55 requests) were addressed to the original Ozias.co, 6% (4 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ozias.co.
Page size can be reduced by 177.7 kB (20%)
907.5 kB
729.8 kB
In fact, the total size of Ozias.co main page is 907.5 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. 25% of websites need less resources to load. Images take 486.1 kB which makes up the majority of the site volume.
Potential reduce by 172.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 172.4 kB or 83% of the original size.
Potential reduce by 4.6 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. Ozias images are well optimized though.
Potential reduce by 222 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 479 B
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. Ozias.co has all CSS files already compressed.
Number of requests can be reduced by 30 (54%)
56
26
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ozias. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
ozias.co
160 ms
ozias.co
443 ms
kadence-splide.min.css
288 ms
kb-blocks-splide.min.css
332 ms
css
27 ms
style.min.css
363 ms
global.min.css
291 ms
header.min.css
297 ms
content.min.css
339 ms
woocommerce.min.css
683 ms
footer.min.css
566 ms
style-blocks-rowlayout.css
610 ms
style-blocks-column.css
602 ms
style-blocks-advancedbtn.css
647 ms
kb-button-deprecated-style.min.css
642 ms
style-blocks-advancedgallery.css
879 ms
style-blocks-infobox.css
915 ms
style-blocks-testimonials.css
886 ms
rankmath.min.css
951 ms
jquery.min.js
954 ms
jquery-migrate.min.js
910 ms
jquery.blockUI.min.js
1139 ms
add-to-cart.min.js
1147 ms
js.cookie.min.js
1176 ms
woocommerce.min.js
1208 ms
jquery.bind-first-0.2.3.min.js
1183 ms
js.cookie-2.1.3.min.js
1241 ms
public.js
1251 ms
email-decode.min.js
1139 ms
navigation.min.js
1414 ms
splide.min.js
1497 ms
kb-splide-init.min.js
1478 ms
lazyload.min.js
1509 ms
ozias2-1.png
275 ms
Ozias-Home.jpg
606 ms
Ozias-Office.jpg
466 ms
Ozias-Public-Speaking.jpg
609 ms
ventura-securities.jpg
519 ms
Sobha-Builders.jpg
533 ms
pnb-metlife.jpg
592 ms
Lodha.jpg
742 ms
Kohler.jpg
807 ms
hg1-logo.jpg
847 ms
Footer24.png
1083 ms
Growth-Graph.jpg
911 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lP.ttf
18 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
31 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
41 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
40 ms
ozias-black.png
632 ms
Google-Partner-Ozias.jpg
764 ms
facebook-marketing-partner.jpg
872 ms
AVA-Digital-Awards.jpg
870 ms
Best-digital-marketing-agency-australia.jpg
906 ms
oziastest1-150x150.jpg
970 ms
oziastest2-150x150.jpg
1069 ms
ozias3-150x150.jpg
1147 ms
SMM-Case-Study-for-Mangallam-768x384.jpg
1166 ms
SEO-Case-Study-for-Shamrock-Concrete-768x384.jpg
1317 ms
SEO-Case-Study-for-HealthGlow-768x384.jpg
1321 ms
embed
219 ms
js
50 ms
ozias.co 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ozias.co 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
ozias.co 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ozias.co 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 Ozias.co 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.
ozias.co
Open Graph data is detected on the main page of Ozias. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: