Access webhathanh.com. Loading...

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value3,130 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.14

78/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

webhathanh.com

2488 ms

bootstrap.css

1421 ms

bootstrap-responsive.css

966 ms

camera.css

1063 ms

style.css

1091 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 69% of them (61 requests) were addressed to the original Webhathanh.com, 12% (11 requests) were made to Static.xx.fbcdn.net and 7% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7.7 sec) relates to the external source Facebook.com.

Content Size

2.6 MB

After Optimization

1.7 MB

In fact, the total size of Webhathanh.com main page is 2.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 42.2 kB

Original 52.5 kB
After minification 35.4 kB
After compression 10.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 17.1 kB, which is 33% 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 42.2 kB or 80% of the original size.

Image Optimization

-20%

Potential reduce by 374.0 kB

Original 1.9 MB
After minification 1.5 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, Webhathanh needs image optimization as it can save up to 374.0 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 333.8 kB

Original 460.4 kB
After minification 379.2 kB
After compression 126.6 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 333.8 kB or 73% of the original size.

CSS Optimization

-86%

Potential reduce by 180.1 kB

Original 209.0 kB
After minification 169.6 kB
After compression 28.9 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. Webhathanh.com needs all CSS files to be minified and compressed as it can save up to 180.1 kB or 86% of the original size.

Requests Now

After Optimization

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

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the interpretation of your content by users in different locales.

High

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

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

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

VI
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webhathanh.com can be misinterpreted by Google and other search engines. Our service has detected that Vietnamese 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 Webhathanh.com 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

webhathanh.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Loading...

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

webhathanh.com

bootstrap.css

bootstrap-responsive.css

camera.css

style.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

webhathanh.com

bootstrap.css

bootstrap-responsive.css

camera.css

style.css

jquery.js

jquery.easing.1.3.js

superfish.js

jquery.ui.totop.js

camera.js

jquery.mobile.customized.min.js

jquery.caroufredsel.js

jquery.touchSwipe.min.js

addthis_widget.js

bootstrap.js

css

css

css

css

css

css

analytics.js

side.aspx

px1.jpg

content_bg.jpg

binder1.png

top1.png

logo-webhathanh.png

hotline-webhathanh.jpg

social_ic1.png

social_ic2.png

book1.png

marker0.png

nav_over.png

nav.png

submenu.jpg

h.png

prev3.png

next3.png

post-thumb-web-hosting1.jpg

thiet-ke-website-tron-goi-webhathanh1.png

thiet-ke-website-cong-ty-webhathanh1.png

thiet-ke-website-ban-hang-webhathanh1.jpg