Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

5a.com

APP Download Page

Page Load Speed

4.2 sec in total

First Response

430 ms

Resources Loaded

3.4 sec

Page Rendered

366 ms

5a.com screenshot

About Website

Welcome to 5a.com homepage info - get ready to check 5 A best content right away, or after learning these important things about 5a.com

一家采用区块链去中心化技术的全球数字货币交易所

Visit 5a.com

Key Findings

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

Performance Metrics

5a.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value22.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.6 s

0/100

25%

SI (Speed Index)

Value22.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

5a.com

430 ms

www.5a.com

536 ms

common.css

6 ms

jquery-3.3.1.min.js

579 ms

jquery.cookie.min.js

14 ms

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

Page Optimization Overview & Recommendations

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

Content Size

217.0 kB

After Optimization

196.6 kB

In fact, the total size of 5a.com main page is 217.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. 25% of websites need less resources to load. CSS take 158.8 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 3.2 kB

  • Original 5.1 kB
  • After minification 5.1 kB
  • After compression 2.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. 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 3.2 kB or 62% of the original size.

JavaScript Optimization

-32%

Potential reduce by 17.0 kB

  • Original 53.1 kB
  • After minification 47.3 kB
  • After compression 36.1 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 17.0 kB or 32% of the original size.

CSS Optimization

-0%

Potential reduce by 295 B

  • Original 158.8 kB
  • After minification 158.5 kB
  • After compression 158.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. 5a.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

11

After Optimization

4

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 5 A. 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.

Accessibility Review

5a.com accessibility score

62

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

5a.com best practices score

75

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

5a.com 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 doesn't use legible font sizes

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 5a.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 5a.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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: