Your Website Score is

Similar Ranking

48
PROPELLERADS - DISPLAY AND MOBILE ADVERTISING NETWORK
propellerads.com
48
HOSTING PLATFORM - GO ONLINE WITH HOSTINGER FOR ONLY $0.99 NOW
hostinger.com
48
PORKBUN.COM | AN ODDLY SATISFYING EXPERIENCE.
porkbun.com
48
NAMEPROS - BUY, SELL, DISCUSS DOMAIN NAMES
namepros.com
48
SINGAPORE PROPERTY AND REAL ESTATE FOR SALE & FOR RENT | 99.CO
99.co
48
STORYBLOCKS BLOG - TELL YOUR STORY WITH VIDEO, AUDIO, AND IMAGES
blog.storyblocks.com
48
TM FORUM - HOW TO MANAGE DIGITAL TRANSFORMATION, AGILE BUSINESS OPERATIONS & CONNECTED DIGITAL ECOSYSTEMS
tmforum.org

Latest Sites

24
THE TRUSTED CPAAS - KALEYRA
kaleyra.com
14
USAHA ADI SANGGORO
uas.co.id
23
JASA OPTIMASI KECEPATAN LOADING WORDPRESS <1 DETIK
wpcepat.com
19
WORDPRESS HOSTING SUPER CEPAT SSD NVME DAN NGINX - CLOUDKU
cloudku.id
59
MONTAGU PRIVATE EQUITY
montagu.com
34
VIDEOCONVERTERHD
videoconverterhd.com

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
CloudFlare
CDN
Nginx
Web Servers
Font Awesome
Font Scripts
Google Tag Manager
Tag Managers
Apache
Web Servers
Twitter Bootstrap
Web Frameworks

48 99.co Last Updated: 2 months

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

Desktop

Mobile

Performance Desktop Score 61%
Best Practices Desktop Score 79%
SEO Desktop Score 92%
Progressive Web App Desktop Score 26%
Performance Mobile Score 17%
Best Practices Mobile Score 79%
SEO Mobile Score 95%
Progressive Web App Mobile Score 29%
Page Authority Authority 51%
Domain Authority Domain Authority 57%
Moz Rank 5.1/10
Bounce Rate Rate 0%
Title Tag 66 Characters
SINGAPORE PROPERTY AND REAL ESTATE FOR SALE & FOR RENT | 99.CO
Meta Description 175 Characters
The best way to find houses, condos, executive condos, rooms & HDBs for sale & rent in Singapore. Unique, authentic real estate and property listings with real photos.
Effective URL 17 Characters
https://www.99.co
Excerpt Page content
Singapore Property and Real Estate for Sale & for Rent | 99.coBuyRentSellResidentialCommercialNew LaunchMortgageNewsSaved searchLogin to see saved searchesSign upLog in99 ResidentialYour way homeThe Fastest Growing Singapore Property WebsiteFor s...
Keywords Cloud Density
rent23 condo22 sale20 sqft16 property14 condos13 beds12 baths11 singapore10 latest8
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
rent 23
condo 22
sale 20
sqft 16
property 14
condos 13
beds 12
baths 11
singapore 10
latest 8
Google Preview Your look like this in google search result
SINGAPORE PROPERTY AND REAL ESTATE FOR SALE & FOR RENT |
https://www.99.co
The best way to find houses, condos, executive condos, rooms & HDBs for sale & rent in Singapore. Unique, authentic real estate and property l
Robots.txt File Detected
Sitemap.xml File Detected
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 2020-05-02 / 7 months
Create on: 2010-04-26 / 11 years
Expires on: 2025-04-25 / 53 months 17 days

TLD Registrar Solutions Ltd. ,BS
Registrar URL: www.tldregistrarsolutions.com
Registrar Email: Please

Nameservers
paul.ns.cloudflare.com
leah.ns.cloudflare.com
Page Size Code & Text Ratio
Document Size: ~326.58 KB
Code Size: ~140.5 KB
Text Size: ~186.08 KB Ratio: 56.98%

Social Data

Delicious Total: 0
Facebook Total: 185,724
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Estimation Traffic and Earnings

110,288
Unique Visits
Daily
204,032
Pages Views
Daily
$197
Income
Daily
3,088,064
Unique Visits
Monthly
5,814,912
Pages Views
Monthly
$4,925
Income
Monthly
35,733,312
Unique Visits
Yearly
68,554,752
Pages Views
Yearly
$52,008
Income
Yearly

Technologies

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 12 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
Minimize main-thread work 2.6 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 310 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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 290 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 2.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce initial server response time Root document took 1,930 ms
Keep the server response time for the main document short because all other requests depend on it
Properly size images Potential savings of 21 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Remove unused JavaScript Potential savings of 455 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
Keep request counts low and transfer sizes small 129 requests • 1,976 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Cumulative Layout Shift 0.003
Cumulative Layout Shift measures the movement of visible elements within the viewport
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 long main-thread tasks 6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoids enormous network payloads Total size was 1,976 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid an excessive DOM size 1,983 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)
Reduce JavaScript execution time 1.4 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 6 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
Serve static assets with an efficient cache policy 14 resources found
A long cache lifetime can speed up repeat visits to your page
Estimated Input Latency 60 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
Defer offscreen images Potential savings of 65 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Minimize third-party usage Third-party code blocked the main thread for 10 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 21 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 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible
Time to Interactive 4.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 18.7 s
A fast page load over a cellular network ensures a good mobile user experience
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
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First CPU Idle 3.2 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/).

Mobile

Mobile Screenshot
First Contentful Paint 3.9 s
First Contentful Paint marks the time at which the first 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
Reduce the impact of third-party code Third-party code blocked the main thread for 510 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
Page load is not fast enough on mobile networks Interactive at 18.6 s
A fast page load over a cellular network ensures a good mobile user experience
Remove unused JavaScript Potential savings of 381 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Enable text compression Potential savings of 25 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoid serving legacy JavaScript to modern browsers Potential savings of 27 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
First Meaningful Paint 3.9 s
First Meaningful Paint measures when the primary content of a page is visible
Max Potential First Input Delay 1,970 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Document uses legible font sizes 98.11% 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
Serve images in next-gen formats Potential savings of 8 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
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
Estimated Input Latency 1,190 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
Time to Interactive 18.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce initial server response time Root document took 2,320 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Tap targets are not sized appropriately 36% 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
Total Blocking Time 2,380 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid large layout shifts 2 elements found
These DOM elements contribute most to the CLS of the page.
First Contentful Paint (3G) 7980 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Keep request counts low and transfer sizes small 120 requests • 1,967 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First CPU Idle 13.7 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/).
Largest Contentful Paint 6.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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 an excessive DOM size 973 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 6 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 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 JavaScript execution time 5.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoids enormous network payloads Total size was 1,967 KiB
Large network payloads cost users real money and are highly correlated with long load times
Properly size images Potential savings of 261 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Serve static assets with an efficient cache policy 13 resources found
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.362
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimize main-thread work 8.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 7.4 s
Speed Index shows how quickly the contents of a page are visibly populated

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
Warning! Your title is not optimized
Description Website
Warning! Your description is not 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
Congratulations! Your Domain Authority is good
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

8,135

Global Rank

235

Indonesia
Traffic
Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
date: Fri, 25 Sep 2020 07:54:13 GMT
content-type: text/html; charset=utf-8
set-cookie: __cfduid=d5f51924399882b5e4cfa13e3d46a55541601020452; expires=Sun, 25-Oct-20 07:54:12 GMT; path=/; domain=.99.co; HttpOnly; SameSite=Lax
x-powered-by: Express
x-request-id: 6a61f2df-de45-9df3-be03-c6c7bd8d377f
x-b3-traceid: 93b7dcff73a13aaaa6854551910cd5e8
x-b3-sampled: 1
vary: Accept-Encoding
x-envoy-upstream-service-time: 272
x-envoy-decorator-operation: spa-web-prod.sg-prod.svc.cluster.local:80/*
set-cookie: country=SG;Max-Age=31536000
cf-cache-status: DYNAMIC
cf-request-id: 0565da76620000caa00b92b200000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 5d832d03df62caa0-YYZ
content-encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments