Tools & Wizards About Us
ozsharing.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ozsharing.com

NameBright - Domain Expired

Page Load Speed

5.8 sec in total

First Response

1.2 sec

Resources Loaded

3.6 sec

Page Rendered

929 ms

ozsharing.com screenshot

About Website

Visit ozsharing.com now to see the best up-to-date Ozsharing content and also check out these interesting facts you probably never knew about ozsharing.com

Visit ozsharing.com

Key Findings

We analyzed Ozsharing.com page load time and found that the first response time was 1.2 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

ozsharing.com performance score

0

Network Requests Diagram

ozsharing.com

1226 ms

main_v2.css

550 ms

less.min.js

7 ms

underscore.js

237 ms

require.js

394 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 43% of them (10 requests) were addressed to the original Ozsharing.com, 35% (8 requests) were made to D1gnyfdrgzv9sa.cloudfront.net and 9% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source D1gnyfdrgzv9sa.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 483.4 kB (9%)

Content Size

5.4 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ozsharing.com main page is 5.4 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. 30% of websites need less resources to load. Images take 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 27.2 kB

  • Original 32.2 kB
  • After minification 22.8 kB
  • After compression 5.0 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. This page needs HTML code to be minified as it can gain 9.4 kB, which is 29% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 27.2 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 125.3 kB

  • Original 5.0 MB
  • After minification 4.8 MB

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. Ozsharing images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 70.4 kB

  • Original 120.0 kB
  • After minification 120.0 kB
  • After compression 49.6 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 70.4 kB or 59% of the original size.

CSS Optimization

-86%

Potential reduce by 260.6 kB

  • Original 303.4 kB
  • After minification 277.1 kB
  • After compression 42.9 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. Ozsharing.com needs all CSS files to be minified and compressed as it can save up to 260.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (33%)

Requests Now

21

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ozsharing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

ozsharing.com

ozsharing.com

1226 ms

main_v2.css

main_v2.css

550 ms

less.min.js

less.min.js

7 ms

underscore.js

underscore.js

237 ms

require.js

require.js

394 ms

jquery.js

jquery.js

393 ms

bootstrap.min.js

bootstrap.min.js

280 ms

angular.min.js

angular.min.js

81 ms

angularjs-main.js

angularjs-main.js

200 ms

css

css

26 ms

bg-custom.jpg

bg-custom.jpg

247 ms

1614423

1614423

756 ms

1614422

1614422

1033 ms

1614421

1614421

1071 ms

1614416

1614416

1007 ms

1614415

1614415

1437 ms

1614414

1614414

542 ms

1614398

1614398

639 ms

1614397

1614397

1803 ms

haifanghui-banner.gif

haifanghui-banner.gif

842 ms

ga.js

ga.js

52 ms

icomoon.woff

icomoon.woff

80 ms

__utm.gif

__utm.gif

12 ms

SEO Factors

ozsharing.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ozsharing.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ozsharing.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.

Social Sharing Optimization

ozsharing.com

Open Graph description is not detected on the main page of Ozsharing. 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: