Tools & Wizards About Us
xptt.com screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

xptt.com

郑永博客

Page Load Speed

7 sec in total

First Response

1.7 sec

Resources Loaded

4.9 sec

Page Rendered

315 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 1.7 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

xptt.com performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

82/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.1 s

64/100

10%

Network Requests Diagram

xptt.com

1701 ms

wp-emoji-release.min.js

245 ms

style.css

665 ms

jquery.min.js

694 ms

jquery.js

835 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 249.7 kB (46%)

Content Size

537.2 kB

After Optimization

287.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xptt.com main page is 537.2 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. Images take 211.5 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 39.0 kB

  • Original 53.1 kB
  • After minification 52.4 kB
  • After compression 14.1 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 39.0 kB or 73% of the original size.

Image Optimization

-8%

Potential reduce by 16.0 kB

  • Original 211.5 kB
  • After minification 195.5 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

-66%

Potential reduce by 112.0 kB

  • Original 168.4 kB
  • After minification 158.0 kB
  • After compression 56.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 112.0 kB or 66% of the original size.

CSS Optimization

-79%

Potential reduce by 82.7 kB

  • Original 104.3 kB
  • After minification 102.7 kB
  • After compression 21.6 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 82.7 kB or 79% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

34

After Optimization

34

  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xptt. According to our analytics all requests are already optimized.

Network Requests Diagram

xptt.com

xptt.com

1701 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

245 ms

style.css

style.css

665 ms

jquery.min.js

jquery.min.js

694 ms

jquery.js

jquery.js

835 ms

zytx.jpg

zytx.jpg

253 ms

search-icon.png

search-icon.png

222 ms

timthumb.php

timthumb.php

309 ms

timthumb.php

timthumb.php

356 ms

timthumb.php

timthumb.php

491 ms

timthumb.php

timthumb.php

713 ms

timthumb.php

timthumb.php

698 ms

timthumb.php

timthumb.php

762 ms

timthumb.php

timthumb.php

909 ms

timthumb.php

timthumb.php

885 ms

timthumb.php

timthumb.php

1136 ms

timthumb.php

timthumb.php

998 ms

timthumb.php

timthumb.php

1014 ms

217f45c3973bcf3a5fa30334714fad26.png

217f45c3973bcf3a5fa30334714fad26.png

1005 ms

bda09c15de8028b03a5165944368f745.png

bda09c15de8028b03a5165944368f745.png

1122 ms

e323e158cc1b16465d87f035dae01544.png

e323e158cc1b16465d87f035dae01544.png

1140 ms

1eafe52c4773cca8e61d53dca73344a8.png

1eafe52c4773cca8e61d53dca73344a8.png

1233 ms

9d7a1fd054cb532d3daac3b19aa70ed3.png

9d7a1fd054cb532d3daac3b19aa70ed3.png

1246 ms

f83826db86d14f4128f146421840db36.png

f83826db86d14f4128f146421840db36.png

1248 ms

a919a439d7eb975febb183f41a0e6fc9.png

a919a439d7eb975febb183f41a0e6fc9.png

1358 ms

fc0f3f74ba5a92ee593a4a159f4dcc16.png

fc0f3f74ba5a92ee593a4a159f4dcc16.png

1354 ms

c1c19d714393cd9b8ea3a1e955db8521.png

c1c19d714393cd9b8ea3a1e955db8521.png

1365 ms

338aab9b039236de24c1d8a5def2dc77.png

338aab9b039236de24c1d8a5def2dc77.png

1465 ms

9894143a7878c1f306f2e1bf05d8d2f0.png

9894143a7878c1f306f2e1bf05d8d2f0.png

1488 ms

329e7691bfa663aa824c09636635e9bc.png

329e7691bfa663aa824c09636635e9bc.png

1480 ms

76ef6668112581e992714664b49a4bc6.png

76ef6668112581e992714664b49a4bc6.png

1573 ms

5aada67c437d23b8238e9122c5a3b941.png

5aada67c437d23b8238e9122c5a3b941.png

1594 ms

056234b874c6f6fc2c167897a05ec834.png

056234b874c6f6fc2c167897a05ec834.png

1592 ms

6048222801e3df54f5c181d9dd77d170.png

6048222801e3df54f5c181d9dd77d170.png

1701 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2231 ms

menu1.jpg

menu1.jpg

1550 ms

Accessibility Review

xptt.com accessibility score

57

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

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

85

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

xptt.com SEO score

92

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: