Report Summary

  • 0

    Performance

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

sjqw.net

世界奇闻-十大未解之谜-历史趣闻故事-诗经蔷薇

Page Load Speed

26.2 sec in total

First Response

1.6 sec

Resources Loaded

24.3 sec

Page Rendered

213 ms

sjqw.net screenshot

About Website

Welcome to sjqw.net homepage info - get ready to check Sjqw best content for China right away, or after learning these important things about sjqw.net

诗经蔷薇为您提供世界奇闻,世界趣味奇闻故事,十大未解之谜,各种中外世界历史趣味故事!

Visit sjqw.net

Key Findings

We analyzed Sjqw.net page load time and found that the first response time was 1.6 sec and then it took 24.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

sjqw.net performance score

0

Network Requests Diagram

sjqw.net

1622 ms

style2016.css

1145 ms

f.js

1216 ms

jquery.min.js

2559 ms

jquery.sgallery.js

797 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 7% of them (6 requests) were addressed to the original Sjqw.net, 15% (14 requests) were made to Pos.baidu.com and 15% (14 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (11.2 sec) relates to the external source Image.sjqw.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 510.9 kB (56%)

Content Size

919.9 kB

After Optimization

409.0 kB

In fact, the total size of Sjqw.net main page is 919.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. 55% of websites need less resources to load. Javascripts take 681.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 21.3 kB

  • Original 27.3 kB
  • After minification 26.4 kB
  • After compression 5.9 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 21.3 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 16.7 kB

  • Original 195.4 kB
  • After minification 178.7 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. Sjqw images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 460.5 kB

  • Original 681.0 kB
  • After minification 589.5 kB
  • After compression 220.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 460.5 kB or 68% of the original size.

CSS Optimization

-76%

Potential reduce by 12.2 kB

  • Original 16.1 kB
  • After minification 14.4 kB
  • After compression 3.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. Sjqw.net needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (49%)

Requests Now

87

After Optimization

44

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

Accessibility Review

sjqw.net accessibility score

53

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

Document doesn't have a <title> element

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

sjqw.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

sjqw.net SEO score

83

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document doesn't have a <title> element

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

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sjqw.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Sjqw.net 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

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