Access cjsdn.net. Java开发网

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value1.6 s

100/100

10%

cjsdn.net

708 ms

www.cjsdn.net

2004 ms

ALL_BG.gif

459 ms

title.gif

669 ms

feed-rss.gif

433 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that all of those requests were addressed to Cjsdn.net and no external sources were called. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Cjsdn.net.

Content Size

62.5 kB

After Optimization

8.2 kB

In fact, the total size of Cjsdn.net main page is 62.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 62.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 54.3 kB

Original 62.5 kB
After minification 52.2 kB
After compression 8.2 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 10.4 kB, which is 17% 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 54.3 kB or 87% of the original size.

Requests Now

After Optimization

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cjsdn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests 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 interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

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

Language and Encoding

Language Detected

ZH
Language Claimed

N/A
Encoding

GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cjsdn.net 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 Cjsdn.net main page’s claimed encoding is gbk. 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

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