Tools & Wizards About Us
xmqiye.net screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

xmqiye.net

&#120&#109&#19971&#22812&#24433&#35270&#50&#48&#50&#52&#26368&#26032&#38498&#32447&#22823&#29255&#25250&#20808&#30475&#95&#55357&#56613&#22909&#30475&...

Page Load Speed

12.6 sec in total

First Response

2.1 sec

Resources Loaded

10.1 sec

Page Rendered

373 ms

xmqiye.net screenshot

About Website

Visit xmqiye.net now to see the best up-to-date Xmqiye content and also check out these interesting facts you probably never knew about xmqiye.net

&#120&#109&#19971&#22812&#24433&#35270&#20026&#24744&#27599&#26085&#26356&#26032&#20840&#32593&#26368&#26032&#30005&#35270&#21095&#21644&#28909&#25773&#30005&#24433&#59&#32858&#38598&#29233&#24773&#12...

Visit xmqiye.net

Key Findings

We analyzed Xmqiye.net page load time and found that the first response time was 2.1 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

xmqiye.net performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.239

52/100

15%

TTI (Time to Interactive)

Value11.0 s

20/100

10%

Network Requests Diagram

xmqiye.net

2099 ms

style.css

2452 ms

index.css

2274 ms

lang.js

2048 ms

config.js

1822 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 91% of them (72 requests) were addressed to the original Xmqiye.net, 3% (2 requests) were made to Hm.baidu.com and 1% (1 request) were made to S22.cnzz.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Xmqiye.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.4 kB (32%)

Content Size

869.7 kB

After Optimization

594.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xmqiye.net main page is 869.7 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. Images take 567.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 117.4 kB

  • Original 144.2 kB
  • After minification 142.4 kB
  • After compression 26.8 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 117.4 kB or 81% of the original size.

Image Optimization

-9%

Potential reduce by 49.1 kB

  • Original 567.5 kB
  • After minification 518.4 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. Xmqiye images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 82.5 kB

  • Original 124.9 kB
  • After minification 119.4 kB
  • After compression 42.4 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 82.5 kB or 66% of the original size.

CSS Optimization

-80%

Potential reduce by 26.4 kB

  • Original 33.0 kB
  • After minification 29.8 kB
  • After compression 6.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. Xmqiye.net needs all CSS files to be minified and compressed as it can save up to 26.4 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (26%)

Requests Now

77

After Optimization

57

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xmqiye.net

xmqiye.net

2099 ms

style.css

style.css

2452 ms

index.css

index.css

2274 ms

lang.js

lang.js

2048 ms

config.js

config.js

1822 ms

jquery.js

jquery.js

3041 ms

common.js

common.js

2335 ms

page.js

page.js

2276 ms

jquery.lazyload.js

jquery.lazyload.js

2274 ms

slide.js

slide.js

2283 ms

index.js

index.js

1828 ms

marquee.js

marquee.js

1830 ms

150x60.gif

150x60.gif

650 ms

bg.png

bg.png

231 ms

logo.gif

logo.gif

248 ms

22-03-06-41-1.gif

22-03-06-41-1.gif

457 ms

19-54-47-69-1.gif

19-54-47-69-1.gif

437 ms

13-11-54-87-1.jpg

13-11-54-87-1.jpg

972 ms

player_2.jpg

player_2.jpg

459 ms

15-34-22-30-1.jpg

15-34-22-30-1.jpg

687 ms

14-09-06-28-1.jpg

14-09-06-28-1.jpg

489 ms

13-59-41-24-1.gif

13-59-41-24-1.gif

655 ms

19-41-06-86-1.gif

19-41-06-86-1.gif

914 ms

lazy.gif

lazy.gif

690 ms

280x58.gif

280x58.gif

729 ms

yycjy.gif

yycjy.gif

872 ms

2014100115584758.gif

2014100115584758.gif

916 ms

235x60.gif

235x60.gif

917 ms

19-35-57-80-1.gif

19-35-57-80-1.gif

969 ms

2014100108460996.gif

2014100108460996.gif

1091 ms

235x60-1.gif

235x60-1.gif

1141 ms

2014100112000586.gif

2014100112000586.gif

1145 ms

22-00-14-28-1.jpg

22-00-14-28-1.jpg

1144 ms

262x65.gif

262x65.gif

1210 ms

22-43-03-80-1.jpg

22-43-03-80-1.jpg

1295 ms

10-17-06-39-1.jpg

10-17-06-39-1.jpg

1959 ms

14-51-49-28-1.jpg

14-51-49-28-1.jpg

1369 ms

960x85.gif

960x85.gif

1371 ms

12-00-05-22-1.gif

12-00-05-22-1.gif

1373 ms

11-56-18-69-1.gif

11-56-18-69-1.gif

1449 ms

11-55-04-53-1.gif

11-55-04-53-1.gif

1619 ms

11-52-41-11-1.gif

11-52-41-11-1.gif

1595 ms

11-50-54-78-1.gif

11-50-54-78-1.gif

1600 ms

11-48-05-27-1.gif

11-48-05-27-1.gif

1601 ms

15-57-15-29-1.jpg

15-57-15-29-1.jpg

1689 ms

16-06-03-26-1.jpg

16-06-03-26-1.jpg

1825 ms

22-11-53-69-1.jpg

22-11-53-69-1.jpg

1828 ms

22-06-46-41-1.jpg

22-06-46-41-1.jpg

1829 ms

280x40.gif

280x40.gif

1936 ms

stat.php

stat.php

1437 ms

23-55-30-58-1.jpg

23-55-30-58-1.jpg

1943 ms

13-47-27-45-1.jpg

13-47-27-45-1.jpg

1813 ms

13-24-01-49-1.jpg

13-24-01-49-1.jpg

1627 ms

960x86-1.jpg

960x86-1.jpg

1611 ms

ico_wap.gif

ico_wap.gif

1812 ms

search.png

search.png

1691 ms

spacer.gif

spacer.gif

1634 ms

tougao.gif

tougao.gif

1605 ms

dinyue.gif

dinyue.gif

1605 ms

topnew.png

topnew.png

1686 ms

topnewj.gif

topnewj.gif

1526 ms

box_head_bg.gif

box_head_bg.gif

1680 ms

li_dot.gif

li_dot.gif

1600 ms

ico_open.gif

ico_open.gif

1602 ms

iuser.png

iuser.png

1554 ms

ico_arrow_up.gif

ico_arrow_up.gif

1644 ms

loading.gif

loading.gif

1567 ms

ibox_head.png

ibox_head.png

1600 ms

stat.htm

stat.htm

247 ms

core.php

core.php

1099 ms

9.gif

9.gif

1650 ms

h.js

h.js

1593 ms

hm.gif

hm.gif

1251 ms

15-22-33-63-1.gif.thumb.gif

15-22-33-63-1.gif.thumb.gif

230 ms

16-27-36-83-44.jpg.thumb.jpg

16-27-36-83-44.jpg.thumb.jpg

244 ms

17-14-04-55-9.jpg.thumb.jpg

17-14-04-55-9.jpg.thumb.jpg

230 ms

17-03-04-47-9.jpg.thumb.jpg

17-03-04-47-9.jpg.thumb.jpg

219 ms

11-00-14-81-11.jpg.thumb.jpg

11-00-14-81-11.jpg.thumb.jpg

325 ms

app.gif

app.gif

1354 ms

Accessibility Review

xmqiye.net 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

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>).

High

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

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

xmqiye.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

xmqiye.net 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

    GBK

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

xmqiye.net

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