Access xhistory.net. xhistory.net

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

xhistory.net

4105 ms

style.css

3845 ms

inc.js

3450 ms

default.js

3848 ms

swfobject.js

3864 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 79% of them (81 requests) were addressed to the original Xhistory.net, 7% (7 requests) were made to Bbs.xhistory.net and 5% (5 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (9.8 sec) relates to the external source Js.users.51.la.

Content Size

963.8 kB

After Optimization

687.5 kB

In fact, the total size of Xhistory.net main page is 963.8 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. 35% of websites need less resources to load. Images take 640.7 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 119.9 kB

Original 137.9 kB
After minification 117.8 kB
After compression 18.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 20.2 kB, which is 15% 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 119.9 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 21.7 kB

Original 640.7 kB
After minification 619.0 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. Xhistory images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 112.0 kB

Original 156.3 kB
After minification 139.9 kB
After compression 44.3 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 72% of the original size.

CSS Optimization

-78%

Potential reduce by 22.7 kB

Original 28.9 kB
After minification 18.0 kB
After compression 6.2 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. Xhistory.net needs all CSS files to be minified and compressed as it can save up to 22.7 kB or 78% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

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

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.

High

Image elements do not have [alt] attributes

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Page is blocked from indexing

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xhistory.net 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 Xhistory.net main page’s claimed encoding is gb2312. 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

xhistory.net

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

Report Summary

Performance

Accessibility

Best Practices

SEO

xhistory.net

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

xhistory.net

style.css

inc.js

default.js

swfobject.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

xhistory.net

style.css

inc.js

default.js

swfobject.js

menu.js

rollpic.css

jquery-1.2.6.min.js

vote.php

vote.php

stat.php

3516258.js

count.php

xhlogo.gif

indexcenter-wx.png

rdn_532c10e10b00a.jpg

stroll_shop_icon2.gif

top_bg.jpg

ico_qq_t.png

ico_sina.gif

navlist20.gif

navlist30.gif

navlist50.gif

navlist60.gif

navlist70.gif

navlist80.gif

5_dmie9__Western_Wall_jpg.gif

1_gasqf__1365466973474_jpg.gif

1_20130404100443_MTI2NDQ3MzUzOQ==_jpg.gif

927_20120803110826_OGFiZDU2YWI4YTM1MzEzMDI3OTU3NWQyYWEzZDUzNmY=.jpg

927_20120719190735_JUNFJURFJUIxJUVBJUNDJUUy.jpg

927.jpg

1_20111117181129_MjIy.jpg

927_20120705150705_MjAxMDA2MjIxNTQzMzUyNjdhNQ==.jpg

927_20120616150634_MDExOHBpYzA0Mjk1cw==.jpg

927_20120604130649_dSUzRDk4MTQxMDg1OSUyQzExOTE2MzA2MzMlMjZmbSUzRDAlMjZncCUzRDA=.jpg

927_20120519160522_MDEzMDAwMDAzMzYyMjQxMjMxNjc5MDQxMTc3NTZfcw==.jpg

927_20120507160533_Mzc5MTY3NF8w.jpg

927_20120430090455_MTAySDE0M0ctMA==.jpg

1_20100513200534_pjyka.jpg

1_20100512190518_ysaja.jpg

1_20120203170220_MzMz.jpg

1_20111214131253_JUI2JUQ4JUJGJUNDJUI2JUZCJUJGJUNCJUI0JUYzJUIzJUI3JUNEJUNCJUQ2JUFFJUMzJUQ0JUI0JUYwJUQyJUM5JUJEJUJCJUMxJUY3.gif