Access test.39.net. 39健康自测_中国最大的在线健康自测平台

test.39.net screenshot

65

Performance

Renders faster than
79% of other websites
51

Accessibility

Visual factors better than
that of 21% of websites
67

Best Practices

More advanced features
available than in
24% of websites
92

SEO

Google-friendlier than
75% of websites

First Response

2.6 sec

Resources Loaded

76.8 sec

Page Rendered

595 ms

test.39.net screenshot

About Website

Click here to check amazing Test 39 content for Mexico. Otherwise, check out these important facts you probably never knew about test.39.net

Visit test.39.net

Key Findings

We analyzed Test.39.net page load time and found that the first response time was 2.6 sec and then it took 77.4 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. Unfortunately, there were 30 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

test.39.net

2592 ms

exam.js

1796 ms

webtrace.js

542 ms

39base.css

2408 ms

testcss.css

1765 ms

Our browser made a total of 294 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Test.39.net, 32% (95 requests) were made to Image.39.net and 15% (43 requests) were made to Pimg.39.net. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Wt.39.net.

Content Size

2.4 MB

After Optimization

1.4 MB

In fact, the total size of Test.39.net main page is 2.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 100.3 kB

Original 122.6 kB
After minification 106.2 kB
After compression 22.3 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.4 kB, which is 13% 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 100.3 kB or 82% of the original size.

Image Optimization

-23%

Potential reduce by 350.7 kB

Original 1.5 MB
After minification 1.1 MB

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, Test 39 needs image optimization as it can save up to 350.7 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 453.2 kB

Original 693.7 kB
After minification 660.3 kB
After compression 240.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 453.2 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 113.3 kB

Original 134.7 kB
After minification 118.0 kB
After compression 21.4 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. Test.39.net needs all CSS files to be minified and compressed as it can save up to 113.3 kB or 84% of the original size.

Requests Now

261

After Optimization

179

The browser has sent 261 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Test 39. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 9 to 1 for CSS 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

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

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

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 Test.39.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 Test.39.net 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

test.39.net

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