Tools & Wizards About Us
391.net screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

391.net

391学习网 - 专业试题网站

Page Load Speed

18.2 sec in total

First Response

5.7 sec

Resources Loaded

11.8 sec

Page Rendered

736 ms

391.net screenshot

About Website

Click here to check amazing 391 content. Otherwise, check out these important facts you probably never knew about 391.net

391学习网--专业试题网站，提供百万典型试题，为广大学习爱好者分享精准的试题答案及详细的试题解析，打造专业的在线做题、在线看题、在线刷题的平台。

Visit 391.net

Key Findings

We analyzed 391.net page load time and found that the first response time was 5.7 sec and then it took 12.6 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

391.net performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value20.0 s

0/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

391.net

5665 ms

iconfont.css

240 ms

font-awesome.min.css

476 ms

jquery.js

717 ms

base.js

727 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 89% of them (25 requests) were addressed to the original 391.net, 7% (2 requests) were made to Hm.baidu.com and 4% (1 request) were made to . The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain 391.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 265.2 kB (30%)

Content Size

891.8 kB

After Optimization

626.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 55.0 kB

  • Original 63.9 kB
  • After minification 47.8 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 16.1 kB, which is 25% 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 55.0 kB or 86% of the original size.

Image Optimization

-18%

Potential reduce by 60.2 kB

  • Original 336.2 kB
  • After minification 275.9 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. Obviously, 391 needs image optimization as it can save up to 60.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 29.3 kB

  • Original 243.4 kB
  • After minification 243.4 kB
  • After compression 214.1 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 29.3 kB or 12% of the original size.

CSS Optimization

-49%

Potential reduce by 120.6 kB

  • Original 248.4 kB
  • After minification 248.3 kB
  • After compression 127.7 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. 391.net needs all CSS files to be minified and compressed as it can save up to 120.6 kB or 49% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (56%)

Requests Now

25

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

391.net

391.net

5665 ms

iconfont.css

iconfont.css

240 ms

font-awesome.min.css

font-awesome.min.css

476 ms

jquery.js

jquery.js

717 ms

base.js

base.js

727 ms

layui.js

layui.js

3070 ms

base.css

base.css

3421 ms

layui.css

layui.css

731 ms

style.css

style.css

2625 ms

swiper.css

swiper.css

956 ms

banner.css

banner.css

960 ms

style.css

style.css

973 ms

swiper.js

swiper.js

2642 ms

lazyLoad.js

lazyLoad.js

1198 ms

clipboard.js

clipboard.js

1225 ms

qrcode.js

qrcode.js

1444 ms

hm.js

hm.js

1301 ms

51943_kadl_8476.png

51943_kadl_8476.png

478 ms

49344_23m4_5560.jpg

49344_23m4_5560.jpg

1718 ms

22446_k4fd_9876.jpg

22446_k4fd_9876.jpg

2381 ms

35668_fjd2_9096.jpg

35668_fjd2_9096.jpg

252 ms

81773_zagk_9965.jpg

81773_zagk_9965.jpg

256 ms

52758_d6fd_4922.png

52758_d6fd_4922.png

1945 ms

22210_l8da_6905.png

22210_l8da_6905.png

2646 ms

22210_l8da_6905.png

22210_l8da_6905.png

2658 ms

iconfont.woff

iconfont.woff

689 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

42 ms

hm.gif

hm.gif

304 ms

Accessibility Review

391.net accessibility score

76

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

391.net best practices score

83

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

391.net SEO score

91

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

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 391.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 391.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

391.net

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