Access 233.com. 233网校-考证就上233网校

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value5,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

233.com

805 ms

www.233.com

14752 ms

master.css

1089 ms

jquery-1.8.3.min.js

7080 ms

stat.php

2176 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original 233.com, 74% (51 requests) were made to Img.233.com and 6% (4 requests) were made to Cb.baidu.com. The less responsive or slowest element that took the longest time to load (18.1 sec) relates to the external source Img.233.com.

Content Size

579.2 kB

After Optimization

294.9 kB

In fact, the total size of 233.com main page is 579.2 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. 30% of websites need less resources to load. HTML takes 248.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 210.9 kB

Original 248.3 kB
After minification 220.0 kB
After compression 37.4 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 28.4 kB, which is 11% 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 210.9 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 4.5 kB

Original 223.1 kB
After minification 218.6 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. 233 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 68.9 kB

Original 107.8 kB
After minification 107.4 kB
After compression 38.8 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 68.9 kB or 64% of the original size.

Requests Now

After Optimization

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 233. 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.

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 semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ZH
Language Claimed

N/A
Encoding

GB2312

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

233.com

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

233网校-考证就上233网校

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

233.com

www.233.com

master.css

jquery-1.8.3.min.js

stat.php

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

233.com

www.233.com

master.css

jquery-1.8.3.min.js

stat.php

cookie-1.0.0.js

index2016.js

0022.jpg

233-top0108.jpg

720-400-6.png

logo233.png

bg2014.png

m.233.com.png

120-tiku.png

120-weixin.png

120-120.png

Avatar.png

l.png

r.png

h580x280.jpg

te1-zixun.png

gwy-zixun.png

580-2801.png

jzs1-zixun.png

580-280.png

yy.jpg

000129.jpg

dashuju.png

150x100.png

line-0.png

jzs1130-248.png

jzs2130-248.png

cfe130-248.png

zaojia130-248.png

aq130-248.png

cy130-248.png

chuji130-248.png

zhongji130-248.png

ccbp130-248.png

jjs130-248.png

zq130-248.png

teacher130-248.png

qh130-248.png

stat.htm