Tools & Wizards About Us
qirimai.com screenshot

Report Summary

  • 0

    Performance

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

qirimai.com

您所访问的域名暂未出售!请email:83570959@qq.com

Page Load Speed

3.3 sec in total

First Response

231 ms

Resources Loaded

2.1 sec

Page Rendered

962 ms

qirimai.com screenshot

About Website

Visit qirimai.com now to see the best up-to-date Qirimai content and also check out these interesting facts you probably never knew about qirimai.com

请email咨询。

Visit qirimai.com

Key Findings

We analyzed Qirimai.com page load time and found that the first response time was 231 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

qirimai.com performance score

0

Network Requests Diagram

index.php

231 ms

common.js

82 ms

tj.js

157 ms

fhtd_jhf1.php

202 ms

fhtd_jhf1.php

215 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Qirimai.com, 54% (32 requests) were made to Fmlb.netlbtu.com and 5% (3 requests) were made to Qirimai.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Js.users.51.la.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.1 kB (11%)

Content Size

321.9 kB

After Optimization

287.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qirimai.com main page is 321.9 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 282.0 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 845 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 417 B

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

Image Optimization

-6%

Potential reduce by 16.0 kB

  • Original 282.0 kB
  • After minification 266.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. Qirimai images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 8.4 kB

  • Original 13.4 kB
  • After minification 12.1 kB
  • After compression 5.0 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 8.4 kB or 63% of the original size.

CSS Optimization

-35%

Potential reduce by 8.8 kB

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

Requests Breakdown

Number of requests can be reduced by 9 (18%)

Requests Now

51

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

index.php

index.php

231 ms

common.js

common.js

82 ms

tj.js

tj.js

157 ms

fhtd_jhf1.php

fhtd_jhf1.php

202 ms

fhtd_jhf1.php

fhtd_jhf1.php

215 ms

21245017.js

21245017.js

1433 ms

154.203.185.85

154.203.185.85

325 ms

ate.css

ate.css

80 ms

zui.css

zui.css

207 ms

xx1.js

xx1.js

141 ms

dh1.js

dh1.js

139 ms

dh.js

dh.js

139 ms

xx2.js

xx2.js

142 ms

1.js

1.js

146 ms

dl.js

dl.js

200 ms

tj.js

tj.js

201 ms

df0515659c031251093942922779f350.gif

df0515659c031251093942922779f350.gif

478 ms

3p960x60.gif

3p960x60.gif

567 ms

skuca7c655a-216d-4805-9a32-22a71ab43d28.gif

skuca7c655a-216d-4805-9a32-22a71ab43d28.gif

439 ms

0103g120009t6ixzyA17F.gif

0103g120009t6ixzyA17F.gif

584 ms

5cduny4gxok12245cduny4gxok4919879.jpg

5cduny4gxok12245cduny4gxok4919879.jpg

437 ms

kf4rdwrjfgt1224kf4rdwrjfgt5019881.jpg

kf4rdwrjfgt1224kf4rdwrjfgt5019881.jpg

321 ms

5i1h5yozhqb12245i1h5yozhqb5119883.jpg

5i1h5yozhqb12245i1h5yozhqb5119883.jpg

320 ms

o5nau2z1hdy1224o5nau2z1hdy5219885.jpg

o5nau2z1hdy1224o5nau2z1hdy5219885.jpg

317 ms

tqks0rmmupi1224tqks0rmmupi5219887.jpg

tqks0rmmupi1224tqks0rmmupi5219887.jpg

315 ms

g1rxanquapq1224g1rxanquapq5319889.jpg

g1rxanquapq1224g1rxanquapq5319889.jpg

314 ms

lgzvdoltnys1224lgzvdoltnys5419891.jpg

lgzvdoltnys1224lgzvdoltnys5419891.jpg

400 ms

o3tur4kb5nc1224o3tur4kb5nc5519893.jpg

o3tur4kb5nc1224o3tur4kb5nc5519893.jpg

369 ms

akivfww3ftv1226akivfww3ftv4819951.jpg

akivfww3ftv1226akivfww3ftv4819951.jpg

367 ms

wrok1kvnf5t1226wrok1kvnf5t4919953.jpg

wrok1kvnf5t1226wrok1kvnf5t4919953.jpg

367 ms

drsvfkz2efq1226drsvfkz2efq5019955.jpg

drsvfkz2efq1226drsvfkz2efq5019955.jpg

389 ms

qp22gnxjvb11226qp22gnxjvb15119957.jpg

qp22gnxjvb11226qp22gnxjvb15119957.jpg

406 ms

yxym2c0gphw1226yxym2c0gphw5119959.jpg

yxym2c0gphw1226yxym2c0gphw5119959.jpg

406 ms

odao2wrrg5d1226odao2wrrg5d5219961.jpg

odao2wrrg5d1226odao2wrrg5d5219961.jpg

405 ms

zvvhddnrb3n1226zvvhddnrb3n5319963.jpg

zvvhddnrb3n1226zvvhddnrb3n5319963.jpg

409 ms

fggyvxgf52k1226fggyvxgf52k5419965.jpg

fggyvxgf52k1226fggyvxgf52k5419965.jpg

498 ms

espak31zrhe1226espak31zrhe0319913.jpg

espak31zrhe1226espak31zrhe0319913.jpg

411 ms

nax312tglyb1226nax312tglyb0419915.jpg

nax312tglyb1226nax312tglyb0419915.jpg

408 ms

w5jxhhyimyd1226w5jxhhyimyd0419917.jpg

w5jxhhyimyd1226w5jxhhyimyd0419917.jpg

406 ms

e2m53w1rvdn1226e2m53w1rvdn0519919.jpg

e2m53w1rvdn1226e2m53w1rvdn0519919.jpg

412 ms

54bxu2o0gde122654bxu2o0gde2719921.jpg

54bxu2o0gde122654bxu2o0gde2719921.jpg

429 ms

cqsez0jby1i1226cqsez0jby1i2819923.jpg

cqsez0jby1i1226cqsez0jby1i2819923.jpg

435 ms

enzvr1ops5b1226enzvr1ops5b2919925.jpg

enzvr1ops5b1226enzvr1ops5b2919925.jpg

434 ms

bt4wzyacv2g1226bt4wzyacv2g3019927.jpg

bt4wzyacv2g1226bt4wzyacv2g3019927.jpg

429 ms

l4zcdyavi4k1241l4zcdyavi4k2020597.jpg

l4zcdyavi4k1241l4zcdyavi4k2020597.jpg

448 ms

onufkacmd0a1241onufkacmd0a2120599.jpg

onufkacmd0a1241onufkacmd0a2120599.jpg

451 ms

ye2iev5sqyi1241ye2iev5sqyi2120601.jpg

ye2iev5sqyi1241ye2iev5sqyi2120601.jpg

450 ms

pd3z1zauk4q1241pd3z1zauk4q2220603.jpg

pd3z1zauk4q1241pd3z1zauk4q2220603.jpg

448 ms

3ycdnsaetlo12413ycdnsaetlo2320605.jpg

3ycdnsaetlo12413ycdnsaetlo2320605.jpg

450 ms

30e4df2irqp124130e4df2irqp2420607.jpg

30e4df2irqp124130e4df2irqp2420607.jpg

451 ms

rjpw3sdezif1241rjpw3sdezif2520609.jpg

rjpw3sdezif1241rjpw3sdezif2520609.jpg

457 ms

adqjxzctzsq1241adqjxzctzsq2620611.jpg

adqjxzctzsq1241adqjxzctzsq2620611.jpg

452 ms

0105g120009t6iw3cE94C.gif

0105g120009t6iw3cE94C.gif

444 ms

hg960x60.gif

hg960x60.gif

470 ms

c8e5fa5348ad491db612e8cd6c47e2e8.gif

c8e5fa5348ad491db612e8cd6c47e2e8.gif

493 ms

video-play.png

video-play.png

172 ms

ynv100.gif

ynv100.gif

227 ms

video-mask.png

video-mask.png

159 ms

ashkad.gif

ashkad.gif

422 ms

Accessibility Review

qirimai.com accessibility score

45

Accessibility Issues

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

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

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

qirimai.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

qirimai.com SEO score

92

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qirimai.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Qirimai.com main page’s claimed encoding is . 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

qirimai.com

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