Your Website Score is

Similar Ranking

5
BOX FPT CHUYÊN CUNG CẤP TIVI BOX FPT VÀ LẮP WIFI FPT TOÀN QUỐC
boxfpt.vn
4
ĐÃ LÀM SEO THÌ PHẢI BIẾT FACESEO
faceseo.vn
4
BAO HO LAO DONG | BẢO HỘ SONG HÀNH . AN TOÀN HƠN - CHUYÊN NGHIỆP HƠN!
baohosonghanh.com
3
TRANG CHỦ - LẮP ĐẶT TRUYỀN HÌNH SỐ
lapdattruyenhinhso.com
3
SNEAKER H2T STORE - PHONG CÁCH, NĂNG ĐỘNG VÀ CÁ TÍNH
h2tstore.net

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

5 boxfpt.vn Last Updated: 1 month

Success 40% of passed verification steps
Warning 30% of total warning
Errors 30% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 74%
Best Practices Desktop Score 79%
SEO Desktop Score 100%
Progressive Web App Desktop Score 41%
Performance Mobile Score 56%
Best Practices Mobile Score 86%
SEO Mobile Score 97%
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
Cumulative Layout Shift 0.233
Cumulative Layout Shift measures the movement of visible elements within the viewport
First CPU Idle 1.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/).
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
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
Remove unused JavaScript Potential savings of 44 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Remove unused CSS Potential savings of 64 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
Reduce initial server response time Root document took 1,180 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Does not use HTTPS 48 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
Avoids an excessive DOM size 364 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)
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
Avoid chaining critical requests 39 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
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 Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids enormous network payloads Total size was 931 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 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimizes main-thread work 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Defer offscreen images Potential savings of 21 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Serve static assets with an efficient cache policy 48 resources found
A long cache lifetime can speed up repeat visits to your page
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
Eliminate render-blocking resources Potential savings of 830 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Meaningful Paint 1.0 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
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Serve images in next-gen formats Potential savings of 39 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
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 2.5 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 64 requests • 931 KiB
To set budgets for the quantity and size of page resources, add a budget.json file

Mobile

Mobile Screenshot
Time to Interactive 9.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint (3G) 7155 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Avoids an excessive DOM size 364 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 Contentful Paint 3.4 s
First Contentful Paint marks the time at which the first text or image is painted
Serve images in next-gen formats Potential savings of 282 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
Minimize third-party usage Third-party code blocked the main thread for 80 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
First Meaningful Paint 3.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 66 requests • 1,310 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
Eliminate render-blocking resources Potential savings of 2,650 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 5.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Efficiently encode images Potential savings of 64 KiB
Optimized images load faster and consume less cellular data
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 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
Serve static assets with an efficient cache policy 48 resources found
A long cache lifetime can speed up repeat visits to your page
Does not use HTTPS 48 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
Tap targets are not sized appropriately 70% 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
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
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
Avoids enormous network payloads Total size was 1,310 KiB
Large network payloads cost users real money and are highly correlated with long load times
Remove unused JavaScript Potential savings of 44 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
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
Avoid chaining critical requests 41 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
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
JavaScript execution time 1.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minimize main-thread work 2.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 6.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay 300 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First CPU Idle 5.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/).
Total Blocking Time 220 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce initial server response time Root document took 1,130 ms
Keep the server response time for the main document short because all other requests depend on it
Remove unused CSS Potential savings of 64 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.
Avoid long main-thread tasks 6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

1,015,176

Global Rank

24,677

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