Your Website Score is

Similar Ranking

19
F.A.C.E. THE AGENCY: TRAINING & BUSINESS DEVELOPMENT FIRM
face-theagency.com
19
HEALTH, FITNESS, AND TRAINING EQUIPMENT | HUNGRY4FITNESS
hungry4fitness.co.uk
19
微赞 - 企业直播营销平台,为企业提供专业微信直播方案(广州赞赏信息科技有限公司)
vzan.com
19
DIGITBINARY.COM - TECHNOLOGY EDUCATION - DIGITAL TRANSFORMATION
digitbinary.com
19
SECOND EARTH FOUNDATION
secondearthfoundation.com
19
GÖÇÜK AKADEMISI BOYASIZ GÖÇÜK DÜZELTME DOLU HASARI ONARIMI
gocukakademisi.com
19
THE PREMIUM MILITARY GEAR COMPANY IN --- - OLIVE PLANET
oliveplanet.in

Latest Sites

2
YOUTUBE
youtu.be
9
YOUTUBE
youtube.com
26
FISHINGTON.IO - PLAY ONLINE!
fishington.io
46
FREE YOUTUBE TO MP3 CONVERTER
yt8s.com
31
DOWNLOAD YOUTUBE VIDEOS ONLINE FOR FREE - Y2MATE
youtubepi.com
19
DONCHECHE CHALLANGE
shop.flairsuppliesgroup.co.uk

Top Technologies

Google Font API
Font Scripts
Nginx
Web Servers
CloudFlare
CDN
Varnish
Cache Tools
Google Tag Manager
Tag Managers
Twitter Bootstrap
Web Frameworks
Font Awesome
Font Scripts
Apache
Web Servers

19 puchonglegenda.com Last Updated: 2 months

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

Desktop

Mobile

Performance Desktop Score 59%
Best Practices Desktop Score 96%
SEO Desktop Score 85%
Performance Mobile Score 34%
Best Practices Mobile Score 96%
SEO Mobile Score 85%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 22 Characters
HOME - PUCHONG LEGENDA
Meta Description 15 Characters
Puchong Legenda
Effective URL 30 Characters
https://www.puchonglegenda.com
Excerpt Page content
Home - Puchong Legenda HOME DEVELOPMENTS RESIDENC...
Meta Keywords 1 Detected
Keywords Cloud Density
puchong18 legenda7 storey6 international5 huges5 bayan5 plan4 school4 sunway4 mall4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
puchong 18
legenda 7
storey 6
international 5
huges 5
bayan 5
plan 4
school 4
sunway 4
mall 4
Google Preview Your look like this in google search result
HOME - PUCHONG LEGENDA
https://www.puchonglegenda.com
Puchong Legenda
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~165.29 KB
Code Size: ~75.97 KB
Text Size: ~89.32 KB Ratio: 54.04%

Social Data

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Serve static assets with an efficient cache policy 8 resources found
A long cache lifetime can speed up repeat visits to your page
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
First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid enormous network payloads Total size was 5,732 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize third-party usage Third-party code blocked the main thread for 140 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
Largest Contentful Paint 3.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 430 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce unused JavaScript Potential savings of 401 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid large layout shifts 2 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Avoid serving legacy JavaScript to modern browsers Potential savings of 18 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](https://philipwalton.com/articles/deploying-es2015-code-in-production-today/) to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Largest Contentful Paint element 3,770 ms
This is the largest contentful element painted within the viewport
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
Cumulative Layout Shift 0.128
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minify CSS Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes
Minify JavaScript Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Speed Index 4.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Potential savings of 2,618 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Total Blocking Time 190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Properly size images Potential savings of 937 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Reduce initial server response time Root document took 1,070 ms
Keep the server response time for the main document short because all other requests depend on it
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
Server Backend Latencies 10 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 unused CSS Potential savings of 78 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Defer offscreen images Potential savings of 378 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Avoid chaining critical requests 63 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 10 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
Time to Interactive 4.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size 537 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)

Mobile

Mobile Screenshot
First Contentful Paint 5.2 s
First Contentful Paint marks the time at which the first text or image is painted
Serve static assets with an efficient cache policy 8 resources found
A long cache lifetime can speed up repeat visits to your page
Reduce initial server response time Root document took 1,120 ms
Keep the server response time for the main document short because all other requests depend on it
Defer offscreen images Potential savings of 61 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
JavaScript execution time 1.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources Potential savings of 2,700 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Total Blocking Time 70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minify JavaScript Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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
Time to Interactive 14.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size 539 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)
Server Backend Latencies 20 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 serving legacy JavaScript to modern browsers Potential savings of 18 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](https://philipwalton.com/articles/deploying-es2015-code-in-production-today/) to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Properly size images Potential savings of 798 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 14.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid enormous network payloads Total size was 3,848 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 2.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint element 14,700 ms
This is the largest contentful element painted within the viewport
Minify CSS Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes
Cumulative Layout Shift 0.582
Cumulative Layout Shift measures the movement of visible elements within the viewport
Network Round Trip Times 10 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
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
Reduce unused JavaScript Potential savings of 402 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Speed Index 11.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts 1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Serve images in next-gen formats Potential savings of 2,045 KiB
Image formats like WebP and AVIF 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 110 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 chaining critical requests 63 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
Reduce unused CSS Potential savings of 78 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
puchonglegenda.co Available
puchonglegenda.us Available
puchonglegenda.com Already Registered
puchonglegenda.org Available
puchonglegenda.net Available
pchonglegenda.com Available
luchonglegenda.com Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Fri, 21 Mar 2025 03:19:54 GMT
Server: Apache
Expires: Sat, 26 Jul 1997 05:00:00 GMT
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Link: ; rel="https://api.w.org/", ; rel="alternate"; title="JSON"; type="application/json", ; rel=shortlink
Upgrade: h2,h2c
Connection: Upgrade
Last-Modified: Fri, 21 Mar 2025 03:19:55 GMT
Content-Type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records