Tools & Wizards About Us
vnhd.net screenshot

Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

vnhd.net

Đang Bảo trì...

Page Load Speed

2.1 sec in total

First Response

27 ms

Resources Loaded

1.8 sec

Page Rendered

214 ms

vnhd.net screenshot

About Website

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

Visit vnhd.net

Key Findings

We analyzed Vnhd.net page load time and found that the first response time was 27 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

vnhd.net performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

vnhd.net

27 ms

phimh.com

637 ms

maximage.css

20 ms

styles.css

36 ms

11.jpg

44 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Vnhd.net, 58% (11 requests) were made to Phimh.com and 16% (3 requests) were made to Lh3.googleusercontent.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Phimh.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 354.9 kB (25%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vnhd.net main page is 1.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. 15% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 3.5 kB

  • Original 5.4 kB
  • After minification 4.6 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 712 B, 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 3.5 kB or 65% of the original size.

Image Optimization

-10%

Potential reduce by 111.5 kB

  • Original 1.1 MB
  • After minification 998.7 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. Vnhd images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 239.4 kB

  • Original 294.9 kB
  • After minification 170.5 kB
  • After compression 55.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 239.4 kB or 81% of the original size.

CSS Optimization

-35%

Potential reduce by 528 B

  • Original 1.5 kB
  • After minification 1.5 kB
  • After compression 988 B

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. Vnhd.net needs all CSS files to be minified and compressed as it can save up to 528 B or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (43%)

Requests Now

14

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vnhd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

vnhd.net

vnhd.net

27 ms

phimh.com

phimh.com

637 ms

maximage.css

maximage.css

20 ms

styles.css

styles.css

36 ms

11.jpg

11.jpg

44 ms

jquery.js

jquery.js

36 ms

jquery.easing.min.js

jquery.easing.min.js

586 ms

jquery.cycle.all.js

jquery.cycle.all.js

599 ms

jquery.maximage.js

jquery.maximage.js

596 ms

jquery.fullscreen.js

jquery.fullscreen.js

590 ms

jquery.ba-hashchange.js

jquery.ba-hashchange.js

586 ms

main.js

main.js

608 ms

33.jpg

33.jpg

47 ms

44.jpg

44.jpg

69 ms

gradient.png

gradient.png

601 ms

css

css

20 ms

full-screen-btn.png

full-screen-btn.png

1105 ms

3XFpErgg3YsZ5fqUU-UIt2E.ttf

3XFpErgg3YsZ5fqUU-UIt2E.ttf

9 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

15 ms

Accessibility Review

vnhd.net accessibility score

56

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

Buttons do not have an accessible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

vnhd.net best practices score

58

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

vnhd.net SEO score

92

Search Engine Optimization Advices

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 uses legible font sizes

Language and Encoding

  • Language Detected

    VI

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vnhd.net can be misinterpreted by Google and other search engines. Our service has detected that Vietnamese is used on the page, and it does not match the claimed English language. Our system also found out that Vnhd.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

vnhd.net

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