Your Website Score is

Similar Ranking

24
VHEARTS | MẠNG XÃ HỘI HÀNG ĐẦU VIỆT NAM
vhearts.net
24
DÂY CÁP THÉP TUẤN ANH - NHÀ NHẬP KHẨU VÀ PHÂN PHỐI
captheptuananh.com
24
BEHANCE
behance.net
24
THIẾT BỊ PHƠI ĐỒ | THIẾT BỊ PHƠI ĐỒ THÔNG MINH
thietbiphoido.com
24
CÔNG TY LUẬT APOLO LAWYERS | LUẬT SƯ GIỎI | CÔNG TY LUẬT | LUẬT SƯ TP.HCM | CÔNG TY LUẬT CHUYÊN NGHIỆP | CÔNG TY LUẬT TẠI TP. HỒ CHÍ MINH | CÔNG TY LUẬT TẠI SÀI GÒN
apolo.com.vn
24
CAMERA QUAY LÉN SIÊU NHỎ KHÔNG DÂY LÀ MÁY NGỤY TRANG XEM TỪ XA
cameraquaylen.vn
23
SEO MANCHESTER | SEO AGENCY MANCHESTER | REQ
seoreq.com

Latest Sites

4
BAO HO LAO DONG | BẢO HỘ SONG HÀNH . AN TOÀN HƠN - CHUYÊN NGHIỆP HƠN!
baohosonghanh.com
19
JUST A MOMENT...
tuongtaccheo.com
32
LIKES ROCK? WE SAY YES!
likesrock.com

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
Nginx
Web Servers
Font Awesome
Font Scripts
CloudFlare
CDN
LiteSpeed
Web Servers
Yoast SEO
SEO
Twitter Bootstrap
Web Frameworks

24 vhearts.net Last Updated: 2 months

Success 62% of passed verification steps
Warning 23% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 75%
Best Practices Desktop Score 54%
SEO Desktop Score 83%
Progressive Web App Desktop Score 11%
Performance Mobile Score 19%
Best Practices Mobile Score 54%
SEO Mobile Score 81%
Progressive Web App Mobile Score 14%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Only Registered Users

Sign up for see all features and reviews about this site

Login

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Time to Interactive 2.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Keep request counts low and transfer sizes small 49 requests • 2,966 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Eliminate render-blocking resources Potential savings of 900 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused JavaScript Potential savings of 689 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Remove unused CSS Potential savings of 61 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Includes front-end JavaScript libraries with known security vulnerabilities 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Largest Contentful Paint 2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Initial server response time was short Root document took 390 ms
Keep the server response time for the main document short because all other requests depend on it
First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Efficiently encode images Potential savings of 50 KiB
Optimized images load faster and consume less cellular data
Use video formats for animated content Potential savings of 326 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Defer offscreen images Potential savings of 976 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
First CPU Idle 2.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Avoid enormous network payloads Total size was 2,966 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift 0.092
Cumulative Layout Shift measures the movement of visible elements within the viewport
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 13.8 s
A fast page load over a cellular network ensures a good mobile user experience
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 1.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Minify JavaScript Potential savings of 295 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Serve images in next-gen formats Potential savings of 146 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
First Contentful Paint 1.4 s
First Contentful Paint marks the time at which the first text or image is painted
Serve static assets with an efficient cache policy 7 resources found
A long cache lifetime can speed up repeat visits to your page
Estimated Input Latency 20 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Avoids an excessive DOM size 390 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Avoid chaining critical requests 23 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Minimizes main-thread work 1.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Potential savings of 60 KiB
Serve images that are appropriately-sized to save cellular data and improve load time

Mobile

Mobile Screenshot
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Avoid chaining critical requests 23 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Page load is not fast enough on mobile networks Interactive at 13.7 s
A fast page load over a cellular network ensures a good mobile user experience
Max Potential First Input Delay 370 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Total Blocking Time 790 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Remove unused JavaScript Potential savings of 693 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce JavaScript execution time 1.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused CSS Potential savings of 61 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Largest Contentful Paint 13.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive 13.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Speed Index 8.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Minify JavaScript Potential savings of 295 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Initial server response time was short Root document took 170 ms
Keep the server response time for the main document short because all other requests depend on it
Serve images in next-gen formats Potential savings of 146 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoids an excessive DOM size 390 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
First CPU Idle 10.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Estimated Input Latency 70 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Serve static assets with an efficient cache policy 7 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Avoid enormous network payloads Total size was 2,957 KiB
Large network payloads cost users real money and are highly correlated with long load times
Includes front-end JavaScript libraries with known security vulnerabilities 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Keep request counts low and transfer sizes small 49 requests • 2,957 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Properly size images Potential savings of 16 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First Contentful Paint 6.8 s
First Contentful Paint marks the time at which the first text or image is painted
Minimize third-party usage Third-party code blocked the main thread for 100 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Eliminate render-blocking resources Potential savings of 5,020 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint (3G) 15160 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Minimize main-thread work 5.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 976 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Efficiently encode images Potential savings of 50 KiB
Optimized images load faster and consume less cellular data
Use video formats for animated content Potential savings of 326 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Tap targets are not sized appropriately 30% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
First Meaningful Paint 6.8 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

358,108

Global Rank

10,584

Vietnam
Traffic
Search

Domain Available

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Only Registered Users

Sign up for see all features and reviews about this site

Login