Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 0

    Best Practices

  • 84

    SEO

    Google-friendlier than
    52% of websites

Page Load Speed

35.1 sec in total

First Response

9.6 sec

Resources Loaded

17.8 sec

Page Rendered

7.8 sec

About Website

Click here to check amazing 22335555 content. Otherwise, check out these important facts you probably never knew about 22335555.com

Visit 22335555.com

Key Findings

We analyzed 22335555.com page load time and found that the first response time was 9.6 sec and then it took 25.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

22335555.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value22.2 s

0/100

10%

TBT (Total Blocking Time)

Value21,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.178

68/100

15%

TTI (Time to Interactive)

Value43.4 s

0/100

10%

Network Requests Diagram

index.php

9561 ms

common.css

179 ms

swiper.css

200 ms

mxdl.shuwon.css

238 ms

tj.js

184 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 93% of them (65 requests) were addressed to the original 22335555.com, 6% (4 requests) were made to Hm.baidu.com and 1% (1 request) were made to Push.zhanzhang.baidu.com. The less responsive or slowest element that took the longest time to load (9.6 sec) belongs to the original domain 22335555.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (16%)

Content Size

7.9 MB

After Optimization

6.6 MB

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

HTML Optimization

-83%

Potential reduce by 82.3 kB

  • Original 99.3 kB
  • After minification 88.3 kB
  • After compression 17.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 11.0 kB, which is 11% 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 82.3 kB or 83% of the original size.

Image Optimization

-15%

Potential reduce by 1.2 MB

  • Original 7.8 MB
  • After minification 6.6 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, 22335555 needs image optimization as it can save up to 1.2 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-46%

Potential reduce by 373 B

  • Original 805 B
  • After minification 731 B
  • After compression 432 B

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 373 B or 46% of the original size.

CSS Optimization

-3%

Potential reduce by 361 B

  • Original 10.3 kB
  • After minification 10.3 kB
  • After compression 10.0 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. 22335555.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

69

After Optimization

65

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

22335555.com accessibility score

55

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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.

SEO Factors

22335555.com SEO score

84

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

    N/A

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 22335555.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), while the claimed language is Chinese. Our system also found out that 22335555.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 description is not detected on the main page of 22335555. 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: