Tools & Wizards About Us
ozakiverse.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ozakiverse.com

iPhone cases | New iPad Cases and Covers | OZAKI

Page Load Speed

5 sec in total

First Response

272 ms

Resources Loaded

3.4 sec

Page Rendered

1.3 sec

ozakiverse.com screenshot

About Website

Visit ozakiverse.com now to see the best up-to-date OZAKI Verse content for Russia and also check out these interesting facts you probably never knew about ozakiverse.com

Buy a New iPad Case and Brand New Design ipad case from Ozaki! One of the best Apple Ipad accessories, iPhone accessories, iPhone Case brand

Visit ozakiverse.com

Key Findings

We analyzed Ozakiverse.com page load time and found that the first response time was 272 ms and then it took 4.7 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

ozakiverse.com performance score

0

Network Requests Diagram

ozakiverse.com

272 ms

reset.css

75 ms

global.css

156 ms

jquery.min.js

51 ms

thw.js

178 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 68% of them (45 requests) were addressed to the original Ozakiverse.com, 8% (5 requests) were made to Facebook.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Img.alicdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (21%)

Content Size

7.7 MB

After Optimization

6.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 22.7 kB

  • Original 30.1 kB
  • After minification 29.3 kB
  • After compression 7.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 22.7 kB or 75% of the original size.

Image Optimization

-20%

Potential reduce by 1.5 MB

  • Original 7.5 MB
  • After minification 6.1 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. Obviously, OZAKI Verse needs image optimization as it can save up to 1.5 MB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 62.6 kB

  • Original 100.5 kB
  • After minification 79.5 kB
  • After compression 38.0 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 62.6 kB or 62% of the original size.

CSS Optimization

-81%

Potential reduce by 37.2 kB

  • Original 45.7 kB
  • After minification 35.7 kB
  • After compression 8.5 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. Ozakiverse.com needs all CSS files to be minified and compressed as it can save up to 37.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (35%)

Requests Now

62

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ozakiverse.com

ozakiverse.com

272 ms

reset.css

reset.css

75 ms

global.css

global.css

156 ms

jquery.min.js

jquery.min.js

51 ms

thw.js

thw.js

178 ms

iscroll.js

iscroll.js

36 ms

imagesLoaded.js

imagesLoaded.js

148 ms

jquery.timers-1.2.js

jquery.timers-1.2.js

150 ms

random.js

random.js

152 ms

mail.js

mail.js

151 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

224 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

227 ms

bg_home.gif

bg_home.gif

87 ms

gtm.js

gtm.js

72 ms

all.js

all.js

175 ms

TB2eTq_jFXXXXa_XXXXXXXXXXXX_!!1658960702.png

TB2eTq_jFXXXXa_XXXXXXXXXXXX_!!1658960702.png

2476 ms

ozaki-nesletter-bg.png

ozaki-nesletter-bg.png

82 ms

border_gray_hor.gif

border_gray_hor.gif

83 ms

logo_ozaki_type.gif

logo_ozaki_type.gif

83 ms

logo_ozaki_1.gif

logo_ozaki_1.gif

80 ms

The-if-Design-Award-2016-.png

The-if-Design-Award-2016-.png

292 ms

OC151_newsAD.png

OC151_newsAD.png

294 ms

OC150_newsAD.jpg

OC150_newsAD.jpg

739 ms

OC555_VideoAD.png

OC555_VideoAD.png

590 ms

OH013_newsAD.png

OH013_newsAD.png

748 ms

BonusCard-newsAD.png

BonusCard-newsAD.png

447 ms

AppleWatch_VideoAD.png

AppleWatch_VideoAD.png

1017 ms

20150206_tapB.gif

20150206_tapB.gif

1470 ms

OT282_video.jpg

OT282_video.jpg

967 ms

OK350_video.jpg

OK350_video.jpg

995 ms

OT223_video.jpg

OT223_video.jpg

1103 ms

OF030_video.jpg

OF030_video.jpg

1047 ms

OC579_video.jpg

OC579_video.jpg

1228 ms

OC563_video.jpg

OC563_video.jpg

1254 ms

OC556_video.jpg

OC556_video.jpg

1306 ms

OA412_video.jpg

OA412_video.jpg

1271 ms

OA406_video.jpg

OA406_video.jpg

1324 ms

OR302_video.jpg

OR302_video.jpg

1451 ms

OF021_video.jpg

OF021_video.jpg

1476 ms

OT290_video.jpg

OT290_video.jpg

1422 ms

social-fb.gif

social-fb.gif

1381 ms

social-twitter.gif

social-twitter.gif

1399 ms

social-pt.gif

social-pt.gif

1454 ms

social-youtube.gif

social-youtube.gif

1472 ms

blog.gif

blog.gif

1497 ms

small_btn_china-2.jpg

small_btn_china-2.jpg

1525 ms

arrow.png

arrow.png

1527 ms

ozaki-close-btn.png

ozaki-close-btn.png

1540 ms

Ozaki-Light.otf

Ozaki-Light.otf

1536 ms

Ozaki-Black.otf

Ozaki-Black.otf

1544 ms

analytics.js

analytics.js

44 ms

conversion_async.js

conversion_async.js

15 ms

fbds.js

fbds.js

81 ms

67 ms

collect

collect

11 ms

collect

collect

68 ms

50 ms

28 ms

53 ms

xd_arbiter.php

xd_arbiter.php

129 ms

xd_arbiter.php

xd_arbiter.php

258 ms

ping

ping

26 ms

7 ms

like.php

like.php

53 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

269 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

300 ms

SEO Factors

ozakiverse.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ozakiverse.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 Ozakiverse.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

ozakiverse.com

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