Tools & Wizards About Us
ozex.io screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

ozex.io

Cryptocurrency Exchange Rankings With the 24*7 Volume & News Updates

Page Load Speed

5.3 sec in total

First Response

1.7 sec

Resources Loaded

3.4 sec

Page Rendered

157 ms

ozex.io screenshot

About Website

Visit ozex.io now to see the best up-to-date Ozex content and also check out these interesting facts you probably never knew about ozex.io

At Ozex.io, you will find top cryptocurrency exchange rankings along with a 24-hour volume, trading pairs, Bitcoin price, total coins, Alexa rank & news.

Visit ozex.io

Key Findings

We analyzed Ozex.io page load time and found that the first response time was 1.7 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

ozex.io performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.141

78/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

ozex.io

1745 ms

css

35 ms

style.min.css

125 ms

style.css

188 ms

font-awesome.min.css

196 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 86% of them (92 requests) were addressed to the original Ozex.io, 11% (12 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Cdn.datatables.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Ozex.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.6 kB (18%)

Content Size

654.0 kB

After Optimization

533.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ozex.io main page is 654.0 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. 55% of websites need less resources to load. Javascripts take 424.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 32.4 kB

  • Original 41.8 kB
  • After minification 39.3 kB
  • After compression 9.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 32.4 kB or 77% of the original size.

Image Optimization

-91%

Potential reduce by 10.4 kB

  • Original 11.5 kB
  • After minification 1.1 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, Ozex needs image optimization as it can save up to 10.4 kB or 91% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-10%

Potential reduce by 44.4 kB

  • Original 424.9 kB
  • After minification 424.5 kB
  • After compression 380.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 33.4 kB

  • Original 175.8 kB
  • After minification 175.4 kB
  • After compression 142.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. Ozex.io needs all CSS files to be minified and compressed as it can save up to 33.4 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 87 (94%)

Requests Now

93

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ozex.io

ozex.io

1745 ms

css

css

35 ms

style.min.css

style.min.css

125 ms

style.css

style.css

188 ms

font-awesome.min.css

font-awesome.min.css

196 ms

style.min.css

style.min.css

194 ms

style.css

style.css

200 ms

dripicons.css

dripicons.css

199 ms

stylesheet.min.css

stylesheet.min.css

387 ms

print.css

print.css

250 ms

style_dynamic.css

style_dynamic.css

257 ms

responsive.min.css

responsive.min.css

258 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

257 ms

custom_css.css

custom_css.css

258 ms

jquery.min.js

jquery.min.js

377 ms

jquery-migrate.min.js

jquery-migrate.min.js

319 ms

html5.js

html5.js

320 ms

feedzy-rss-feeds.css

feedzy-rss-feeds.css

320 ms

celp-styles.min.css

celp-styles.min.css

320 ms

cmc-icons.min.css

cmc-icons.min.css

381 ms

bootstrap.min.css

bootstrap.min.css

382 ms

qode-like.min.js

qode-like.min.js

382 ms

core.min.js

core.min.js

452 ms

accordion.min.js

accordion.min.js

502 ms

menu.min.js

menu.min.js

503 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

504 ms

wp-polyfill.min.js

wp-polyfill.min.js

505 ms

dom-ready.min.js

dom-ready.min.js

505 ms

hooks.min.js

hooks.min.js

504 ms

i18n.min.js

i18n.min.js

519 ms

a11y.min.js

a11y.min.js

521 ms

autocomplete.min.js

autocomplete.min.js

522 ms

controlgroup.min.js

controlgroup.min.js

522 ms

checkboxradio.min.js

checkboxradio.min.js

523 ms

button.min.js

button.min.js

524 ms

datepicker.min.js

datepicker.min.js

567 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

532 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

47 ms

absolute.js

absolute.js

63 ms

mouse.min.js

mouse.min.js

531 ms

resizable.min.js

resizable.min.js

486 ms

draggable.min.js

draggable.min.js

428 ms

dialog.min.js

dialog.min.js

419 ms

droppable.min.js

droppable.min.js

434 ms

progressbar.min.js

progressbar.min.js

438 ms

selectable.min.js

selectable.min.js

438 ms

sortable.min.js

sortable.min.js

393 ms

slider.min.js

slider.min.js

387 ms

spinner.min.js

spinner.min.js

388 ms

tooltip.min.js

tooltip.min.js

435 ms

tabs.min.js

tabs.min.js

442 ms

effect.min.js

effect.min.js

386 ms

effect-blind.min.js

effect-blind.min.js

386 ms

effect-bounce.min.js

effect-bounce.min.js

386 ms

effect-clip.min.js

effect-clip.min.js

386 ms

effect-drop.min.js

effect-drop.min.js

381 ms

effect-explode.min.js

effect-explode.min.js

384 ms

effect-fade.min.js

effect-fade.min.js

383 ms

effect-fold.min.js

effect-fold.min.js

383 ms

effect-highlight.min.js

effect-highlight.min.js

315 ms

effect-pulsate.min.js

effect-pulsate.min.js

268 ms

effect-size.min.js

effect-size.min.js

314 ms

effect-scale.min.js

effect-scale.min.js

329 ms

effect-shake.min.js

effect-shake.min.js

323 ms

effect-slide.min.js

effect-slide.min.js

323 ms

effect-transfer.min.js

effect-transfer.min.js

323 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

27 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff

40 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff

44 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrc.woff

57 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff

56 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff

55 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

55 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrc.woff

55 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff

56 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDrMfJg.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDrMfJg.woff

57 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMDrMfJg.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMDrMfJg.woff

58 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDrMfJg.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDrMfJg.woff

58 ms

plugins.js

plugins.js

386 ms

jquery.carouFredSel-6.2.1.min.js

jquery.carouFredSel-6.2.1.min.js

360 ms

lemmon-slider.min.js

lemmon-slider.min.js

368 ms

jquery.fullPage.min.js

jquery.fullPage.min.js

368 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

367 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

499 ms

jquery.isotope.min.js

jquery.isotope.min.js

500 ms

packery-mode.pkgd.min.js

packery-mode.pkgd.min.js

446 ms

jquery.stretch.js

jquery.stretch.js

424 ms

imagesloaded.js

imagesloaded.js

421 ms

rangeslider.min.js

rangeslider.min.js

420 ms

jquery.event.move.js

jquery.event.move.js

418 ms

jquery.twentytwenty.js

jquery.twentytwenty.js

413 ms

TweenLite.min.js

TweenLite.min.js

406 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

397 ms

smoothPageScroll.min.js

smoothPageScroll.min.js

397 ms

default_dynamic.js

default_dynamic.js

395 ms

default.min.js

default.min.js

517 ms

custom_js.js

custom_js.js

428 ms

comment-reply.min.js

comment-reply.min.js

387 ms

wp-embed.min.js

wp-embed.min.js

384 ms

tableHeadFixer.js

tableHeadFixer.js

381 ms

numeral.min.js

numeral.min.js

383 ms

celp-ex-list.min.js

celp-ex-list.min.js

431 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

553 ms

close_side_menu.png

close_side_menu.png

393 ms

ozex.io_.svg

ozex.io_.svg

385 ms

logo.png

logo.png

386 ms

logo_black.png

logo_black.png

492 ms

Accessibility Review

ozex.io accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ozex.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ozex.io SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Ozex.io 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 Ozex.io 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

ozex.io

Open Graph data is detected on the main page of Ozex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: