Tools & Wizards About Us
399.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

399.com

Page Load Speed

3.2 sec in total

First Response

374 ms

Resources Loaded

2.7 sec

Page Rendered

119 ms

399.com screenshot

About Website

Visit 399.com now to see the best up-to-date 399 content for United States and also check out these interesting facts you probably never knew about 399.com

Visit 399.com

Key Findings

We analyzed 399.com page load time and found that the first response time was 374 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

399.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

399.com

374 ms

index_1.gif

37 ms

index_2.jpg

49 ms

index_3.gif

51 ms

spacer.gif

53 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 85% of them (17 requests) were addressed to the original 399.com, 10% (2 requests) were made to Js.users.51.la and 5% (1 request) were made to Icon.51.la. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Js.users.51.la.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.5 kB (68%)

Content Size

8.2 kB

After Optimization

2.7 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-79%

Potential reduce by 3.2 kB

  • Original 4.0 kB
  • After minification 3.8 kB
  • After compression 846 B

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 3.2 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 19 B

  • Original 324 B
  • After minification 305 B

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. 399 images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 2.3 kB

  • Original 3.8 kB
  • After minification 3.8 kB
  • After compression 1.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 2.3 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (68%)

Requests Now

19

After Optimization

6

  • Images
  • JavaScript

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

Network Requests Diagram

399.com

399.com

374 ms

index_1.gif

index_1.gif

37 ms

index_2.jpg

index_2.jpg

49 ms

index_3.gif

index_3.gif

51 ms

spacer.gif

spacer.gif

53 ms

index_4.gif

index_4.gif

52 ms

index_5.gif

index_5.gif

52 ms

index_6.gif

index_6.gif

57 ms

index_7.gif

index_7.gif

70 ms

index_8.gif

index_8.gif

72 ms

index_9.gif

index_9.gif

77 ms

index_10.gif

index_10.gif

142 ms

index_11.gif

index_11.gif

98 ms

1889942.js

1889942.js

1106 ms

17107302.js

17107302.js

1836 ms

index_12.gif

index_12.gif

73 ms

index_13.gif

index_13.gif

87 ms

index_14.gif

index_14.gif

89 ms

index_15.gif

index_15.gif

95 ms

icon_0.gif

icon_0.gif

723 ms

Accessibility Review

399.com accessibility score

57

Accessibility Issues

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

399.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

399.com SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

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

399.com

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