Tools & Wizards About Us
xptt.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

xptt.com

郑永博客

Page Load Speed

1.8 sec in total

First Response

561 ms

Resources Loaded

1.1 sec

Page Rendered

140 ms

xptt.com screenshot

About Website

Click here to check amazing Xptt content for China. Otherwise, check out these important facts you probably never knew about xptt.com

关注博客和手机以及互联网，记录生活点滴，分享所见所闻。

Visit xptt.com

Key Findings

We analyzed Xptt.com page load time and found that the first response time was 561 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

xptt.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

xptt.com

561 ms

style.css

74 ms

jquery-1.7.2.min.js

206 ms

adsbygoogle.js

100 ms

activate-power-mode.js

120 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 80% of them (8 requests) were addressed to the original Xptt.com, 20% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (561 ms) belongs to the original domain Xptt.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.1 kB (8%)

Content Size

524.6 kB

After Optimization

480.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xptt.com main page is 524.6 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. 15% of websites need less resources to load. Javascripts take 284.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 32.2 kB

  • Original 42.5 kB
  • After minification 38.0 kB
  • After compression 10.3 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 4.6 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 32.2 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 1.3 kB

  • Original 186.5 kB
  • After minification 185.2 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. Xptt images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 7.3 kB

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

CSS Optimization

-29%

Potential reduce by 3.3 kB

  • Original 11.2 kB
  • After minification 11.2 kB
  • After compression 7.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. Xptt.com needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 29% of the original size.

Requests Breakdown

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

Requests Now

9

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xptt.com

xptt.com

561 ms

style.css

style.css

74 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

206 ms

adsbygoogle.js

adsbygoogle.js

100 ms

activate-power-mode.js

activate-power-mode.js

120 ms

zy.js

zy.js

121 ms

light.png

light.png

60 ms

zhengyong.jpg

zhengyong.jpg

70 ms

2.jpg

2.jpg

298 ms

show_ads_impl.js

show_ads_impl.js

226 ms

Accessibility Review

xptt.com accessibility score

73

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

Links do not have a discernible name

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

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

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

xptt.com 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

High

Page has valid source maps

SEO Factors

xptt.com SEO score

83

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

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xptt.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Xptt.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

xptt.com

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