Your Website Score is

Similar Ranking

26
THIẾT KẾ WEBSITE CHUẨN SEO GIÁ RẺ CHUYÊN NGHIỆP - CAM RANH MEDIA
camranhmedia.com
26
IMGUR: THE MAGIC OF THE INTERNET
imgur.com
26
VẠN PHÁT LAND - CHUYÊN MUA BÁN CHO THUÊ CHUNG CƯ, NHÀ PHỐ, ĐẤT NỀN, DỰ ÁN - THUÊ NHÀ DỄ DÀNG, HỖ TRỢ TÌM NHÀ TRONG VÒNG 7 NGÀY, VỚI NHIỀU GIÁ TỪ THẤP ĐẾN CAO, QUÝ KHÁCH CÓ THỂ LỰA CHỌN TÙY THEO NHU CẦ
vanphatland.vn
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

Latest Sites

3
TRANG CHỦ - LẮP ĐẶT TRUYỀN HÌNH SỐ
lapdattruyenhinhso.com
19
NỘI THẤT CHÂU ÂU CAO CẤP GIÁ RẺ ĐƯỢC NHẬP KHẨU UY TÍN VÀ CHẤT LƯỢNG
cuathepchauau.com
48
LIKESTOOL.COM - GET INSTAGRAM FOLLOWERS, FACEBOOK LIKES, YOUTUBE VIEWS, TWITTER FOLLOWERS AND MORE
likestool.com
19
MÀNG XỐP GÓI HÀNG UY TÍN CHẤT LƯỢNG - NHẬN CUNG CẤP TOÀN QUỐC.
mangxopgoihang.com
23
VÁCH NGĂN CÁCH NHIỆT HẢI VIỆT CHẤT LƯỢNG TỐT GIÁ RẺ
vachngancachnhiet.vn

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
LiteSpeed
Web Servers
Nginx
Web Servers
Font Awesome
Font Scripts
CloudFlare
CDN
Yoast SEO
SEO
WooCommerce
Ecommerce

26 vanphatland.vn Last Updated: 1 month

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

Desktop

Mobile

Performance Desktop Score 79%
Best Practices Desktop Score 86%
SEO Desktop Score 100%
Progressive Web App Desktop Score 37%
Performance Mobile Score 56%
Best Practices Mobile Score 86%
SEO Mobile Score 100%
Progressive Web App Mobile Score 39%
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
Remove unused CSS Potential savings of 46 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
First Meaningful Paint 1.5 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
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
Does not use HTTPS 30 insecure requests 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
Time to Interactive 1.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Eliminate render-blocking resources Potential savings of 840 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Estimated Input Latency 10 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
First CPU Idle 1.5 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/).
Serve images in next-gen formats Potential savings of 40 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
Keep request counts low and transfer sizes small 44 requests • 1,026 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Speed Index 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Initial server response time was short Root document took 430 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoids enormous network payloads Total size was 1,026 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint 2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Minimizes main-thread work 0.4 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 82 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
First Contentful Paint 1.5 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Remove unused JavaScript Potential savings of 21 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Properly size images Potential savings of 82 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
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
Avoids an excessive DOM size 172 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)
Serve static assets with an efficient cache policy 34 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 33 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

Mobile

Mobile Screenshot
Largest Contentful Paint 8.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoids an excessive DOM size 172 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 33 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
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
First Contentful Paint 3.8 s
First Contentful Paint marks the time at which the first text or image is painted
Tap targets are sized appropriately 100% 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
Serve static assets with an efficient cache policy 34 resources found
A long cache lifetime can speed up repeat visits to your page
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
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
Total Blocking Time 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve images in next-gen formats Potential savings of 63 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
Avoid large layout shifts 2 elements found
These DOM elements contribute most to the CLS of the page.
Minimizes main-thread work 1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short Root document took 300 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Max Potential First Input Delay 140 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimize third-party usage Third-party code blocked the main thread for 20 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
Remove unused JavaScript Potential savings of 21 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Does not use HTTPS 30 insecure requests 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
Remove unused CSS Potential savings of 47 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
Time to Interactive 6.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint (3G) 7487 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Meaningful Paint 3.8 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids enormous network payloads Total size was 1,040 KiB
Large network payloads cost users real money and are highly correlated with long load times
Estimated Input Latency 10 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
Keep request counts low and transfer sizes small 44 requests • 1,040 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Properly size images Potential savings of 12 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First CPU Idle 4.3 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/).
Speed Index 5.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 2,460 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

2,278,247

Global Rank

17,558

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