Access 223.so. 域名到期-域名续费提醒

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

223.so

4139 ms

default.htm

1141 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original 223.so, 50% (1 request) were made to 2345.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain 223.so.

Content Size

904.5 kB

After Optimization

740.4 kB

In fact, the total size of 223.so main page is 904.5 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 691.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 112.9 kB

Original 152.8 kB
After minification 145.5 kB
After compression 39.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 112.9 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 3.3 kB

Original 691.7 kB
After minification 688.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. 223 images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 47.9 kB

Original 60.0 kB
After minification 56.6 kB
After compression 12.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 47.9 kB or 80% of the original size.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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 223.so 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 223.so 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

223.so

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