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 behance.net Last Updated: 11 months

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

Desktop

Mobile

Performance Desktop Score 86%
Best Practices Desktop Score 85%
SEO Desktop Score 91%
Progressive Web App Desktop Score 31%
Performance Mobile Score 43%
Best Practices Mobile Score 85%
SEO Mobile Score 88%
Progressive Web App Mobile Score 33%
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
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 7 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
Avoid an excessive DOM size 3,480 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)
Minify JavaScript Potential savings of 144 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 218 requests • 12,505 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 202 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 670 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 2.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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 11.9 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 170 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
Remove unused CSS Potential savings of 25 KB
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
Serve images in next-gen formats Potential savings of 7,481 KB
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
Reduce server response times (TTFB) Root document took 840 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 110 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 4,141 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 30 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
Total Blocking Time 510 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 1.8 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 1,610 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Properly size images Potential savings of 5,366 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 2.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).
Avoid enormous network payloads Total size was 12,505 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted

Mobile

Mobile Screenshot
Serve images in next-gen formats Potential savings of 13,384 KB
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
Reduce server response times (TTFB) Root document took 760 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 480 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 9,426 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 340 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
Total Blocking Time 2,790 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 7.2 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 1,665 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Properly size images Potential savings of 911 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 6.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 10.0 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 19,278 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 12.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 2.7 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 7 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
Avoid an excessive DOM size 3,490 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)
Minify JavaScript Potential savings of 144 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 2.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 222 requests • 19,278 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 206 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 2,490 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 11.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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 at 11.6 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 5475 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 1,600 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
Tap targets are not sized appropriately 52% 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 83.87% 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 CSS Potential savings of 25 KB
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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

308

Global Rank

150

India
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