Your Website Score is

Similar Ranking

22
ACCESO: CUENTAS DE GOOGLE
profiles.google.com
22
LYTSHOP THỜI TRANG SỐ | THỜI TRANG DÀNH CHO GIỚI TRẺ
lytshop.net
22
NHÀ THUỐC 115 BÁN THUỐC CHỮA BỆNH XUẤT TINH SỚM YẾU SINH LÝ TỐT NHẤT
thuoc115.com
22
CÔNG TY MAY ĐỒNG PHỤC HỌC SINH, CÔNG SỞ, Y TẾ - ĐỒNG PHỤC UNICORN
dongphucunicorn.com
22
TRANG CHỦ
landvanphu.com.vn
21
THIÊN ĐƯỜNG MỸ PHẨM LÀM ĐẸP CAO CẤP – MỸ PHẨM ELA
elabeauty.com.vn
19
ELLO | THE CREATORS NETWORK
ello.co

Latest Sites

11
TĂNG LIKE TƯƠNG TÁC CHÉO, TUONGTACCHEO, TĂNG SUB, TĂNG TRAO ĐỔI SUB, TRAODOISUB, TUONGTACCHEO, TĂNG TƯƠNG TÁC CHÉO MẠNG XÃ HỘI
tuongtaccheo.com
24
FUN FACTS 4U - THE FUN KNOWLEDGE ENCYCLOPEDIA
funfacts4u.com
24
NHỮNG ĐIỀU BẠN CẦN BIẾT ĐỂ KHỞI NGHIỆP THÀNH CÔNG!
khoinghiep.top
34
VIỄN THÔNG MOBIFONE GÒ VẤP > DỊCH VỤ MOBIFONE
vnmobifone.vn
39
LIKE4LIKE.ORG - GET 100% FREE FACEBOOK LIKES RIGHT NOW!
like4like.org
19
LIKECOUPON - BLOG CHIA SẺ MÃ GIẢM GIÁ HOSTING,DOMAIN, VPS/SERVER VÀ THEME/PLUGIN WORDPRESS
likecoupon.net

Top Technologies

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

22 landvanphu.com.vn Last Updated: 4 months

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

Desktop

Mobile

Performance Mobile Score 7%
Best Practices Mobile Score 64%
SEO Mobile Score 93%
Progressive Web App Mobile Score 32%
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

Mobile

Mobile Screenshot
Reduce initial server response time Root document took 890 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid chaining critical requests 42 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 360 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
Minimize main-thread work 10.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve images in next-gen formats Potential savings of 4,360 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 (3G) 7998 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Serve static assets with an efficient cache policy 86 resources found
A long cache lifetime can speed up repeat visits to your page
Page load is not fast enough on mobile networks Interactive at 40.3 s
A fast page load over a cellular network ensures a good mobile user experience
Keep request counts low and transfer sizes small 150 requests • 9,823 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Remove duplicate modules in JavaScript bundles Potential savings of 1 KiB
Remove large, duplicate JavaScript modules from bundles 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 enormous network payloads Total size was 9,823 KiB
Large network payloads cost users real money and are highly correlated with long load times
User Timing marks and measures 7 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
First CPU Idle 9.1 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/).
Time to Interactive 40.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size 636 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
Remove unused JavaScript Potential savings of 877 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Meaningful Paint 4.5 s
First Meaningful Paint measures when the primary content of a page is visible
Cumulative Layout Shift 0.486
Cumulative Layout Shift measures the movement of visible elements within the viewport
Document uses legible font sizes 99.92% 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
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
Reduce the impact of third-party code Third-party code blocked the main thread for 2,090 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
Reduce JavaScript execution time 6.6 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
Efficiently encode images Potential savings of 3,070 KiB
Optimized images load faster and consume less cellular data
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Properly size images Potential savings of 2,553 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Eliminate render-blocking resources Potential savings of 3,660 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Defer offscreen images Potential savings of 3,927 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 17.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 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
Enable text compression Potential savings of 155 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Total Blocking Time 2,520 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused CSS Potential savings of 109 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
Max Potential First Input Delay 870 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 4.5 s
First Contentful Paint marks the time at which the first text or image is painted
Minify JavaScript Potential savings of 10 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Largest Contentful Paint 34.8 s
Largest Contentful Paint marks the time at which the largest 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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

4,089,469

Global Rank

4,089,469

Global
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