Report Summary

  • 79

    Performance

    Renders faster than
    86% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 0

    Best Practices

  • 77

    SEO

    Google-friendlier than
    36% of websites

exchanger.cc

Круглосуточный обмен криптовалют

Page Load Speed

3.7 sec in total

First Response

1.6 sec

Resources Loaded

2 sec

Page Rendered

120 ms

exchanger.cc screenshot

About Website

Click here to check amazing Exchanger content. Otherwise, check out these important facts you probably never knew about exchanger.cc

Visit exchanger.cc

Key Findings

We analyzed Exchanger.cc page load time and found that the first response time was 1.6 sec and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

exchanger.cc performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.32

36/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

exchanger.cc

1581 ms

default.css

202 ms

JsHttpRequest.js

223 ms

behaviour.js

120 ms

utils.js

197 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that all of those requests were addressed to Exchanger.cc and no external sources were called. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Exchanger.cc.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.5 kB (62%)

Content Size

61.7 kB

After Optimization

23.2 kB

In fact, the total size of Exchanger.cc main page is 61.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 37.4 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 2.1 kB

  • Original 3.3 kB
  • After minification 3.3 kB
  • After compression 1.2 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 2.1 kB or 63% of the original size.

Image Optimization

-25%

Potential reduce by 2.7 kB

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

JavaScript Optimization

-68%

Potential reduce by 25.4 kB

  • Original 37.4 kB
  • After minification 37.1 kB
  • After compression 12.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 25.4 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 8.4 kB

  • Original 10.2 kB
  • After minification 7.5 kB
  • After compression 1.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. Exchanger.cc needs all CSS files to be minified and compressed as it can save up to 8.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (57%)

Requests Now

7

After Optimization

3

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

Accessibility Review

exchanger.cc accessibility score

77

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

SEO Factors

exchanger.cc SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exchanger.cc can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Exchanger.cc main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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