33 city24.ee Last Updated: 2 weeks

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

Desktop Speed Score

Mobile Speed Score

Performance Desktop Score 62%
Best Practices Desktop Score 47%
SEO Desktop Score 75%
Progressive Web App Desktop Score 0%
Performance Mobile Score 27%
Best Practices Mobile Score 80%
SEO Mobile Score 72%
Progressive Web App Mobile Score 75%
Page Authority Authority 43%
Domain Authority Domain Authority 42%
Moz Rank 4.3/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 66 Characters
KINNISVARA CITY24 - KORTERID MAJAD ÄRIPINNAD MAA OST MÜÜK RENT ÜÜR
Meta Description 57 Characters
City24 Kinnisvara – korterid, majad, maatükid, äripinnad!
Effective URL 21 Characters
https://www.city24.ee
Excerpt Page content
Kinnisvara City24 - korterid majad äripinnad maa ost müük rent üür Eesti Läti Leedu INTERNATIONAL Lemmikud Minu otsingud EST ENGESTFINRUS Logi sisse Logi sisse Loo kasutaja Logi sisse läbi Google Logi sisse läbi Facebook Lisa kuulutus Müük Üür Uusarendused 360° tuur...
Keywords Cloud Density
tallinn95 linnaosa94 vald37 kesklinna35 tartu35 küla28 linn23 müük18 lasnamäe18 haabersti14
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
tallinn 95
linnaosa 94
vald 37
kesklinna 35
tartu 35
küla 28
linn 23
müük 18
lasnamäe 18
haabersti 14
Google Preview Your look like this in google search result
KINNISVARA CITY24 - KORTERID MAJAD ÄRIPINNAD MAA OST MÜÜK RE
https://www.city24.ee
City24 Kinnisvara – korterid, majad, maatükid, äripinnad!
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~378.75 KB
Code Size: ~306.82 KB
Text Size: ~71.93 KB Ratio: 18.99%

city24.ee Estimation Traffic and Earnings

81,542
Unique Visits
Daily
150,852
Pages Views
Daily
$146
Income
Daily
2,283,176
Unique Visits
Monthly
4,299,282
Pages Views
Monthly
$3,650
Income
Monthly
26,419,608
Unique Visits
Yearly
50,686,272
Pages Views
Yearly
$38,544
Income
Yearly

Web Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop Speed Score

Desktop Screenshot
Remove unused JavaScript Potential savings of 575 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
Reduce initial server response time Root document took 1,800 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.
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Avoid serving legacy JavaScript to modern browsers Potential savings of 40 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Serve static assets with an efficient cache policy 84 resources found
A long cache lifetime can speed up repeat visits to your page
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
Enable text compression Potential savings of 73 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Properly size images Potential savings of 324 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Max Potential First Input Delay 170 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Time to Interactive 4.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint 3.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid an excessive DOM size 3,262 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 Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Eliminate render-blocking resources Potential savings of 80 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Minify CSS Potential savings of 14 KiB
Minifying CSS files can reduce network payload sizes
Cumulative Layout Shift 0.047
Cumulative Layout Shift measures the movement of visible elements within the viewport
Serve images in next-gen formats Potential savings of 881 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
Speed Index 3.3 s
Speed Index shows how quickly the contents of a page are visibly populated
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
First CPU Idle 2.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/).
Total Blocking Time 60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid chaining critical requests 15 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
Efficiently encode images Potential savings of 96 KiB
Optimized images load faster and consume less cellular data
Keep request counts low and transfer sizes small 339 requests • 3,927 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minify JavaScript Potential savings of 85 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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
Avoid enormous network payloads Total size was 3,927 KiB
Large network payloads cost users real money and are highly correlated with long load times
Does not use HTTPS 1 insecure request 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 served over 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
Minimizes main-thread work 1.3 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,112 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Remove unused CSS Potential savings of 69 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

Mobile Speed Score

Mobile Screenshot
Avoid serving legacy JavaScript to modern browsers Potential savings of 19 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
Serve images in next-gen formats Potential savings of 331 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
Initial server response time was short Root document took 180 ms
Keep the server response time for the main document short because all other requests depend on it
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 360 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
First CPU Idle 16.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/).
Speed Index 14.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 740 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused JavaScript Potential savings of 720 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
robots.txt is not valid 7 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Remove unused CSS Potential savings of 62 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
First Contentful Paint (3G) 27983 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Reduce JavaScript execution time 4.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Serve static assets with an efficient cache policy 16 resources found
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 17.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Enable text compression Potential savings of 48 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
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
Minimize main-thread work 5.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoids an excessive DOM size 288 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)
Avoids enormous network payloads Total size was 2,491 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Meaningful Paint 14.0 s
First Meaningful Paint measures when the primary content of a page is visible
Cumulative Layout Shift 0.004
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid chaining critical requests 11 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 large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Max Potential First Input Delay 1,090 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 14.0 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 18.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Estimated Input Latency 650 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 multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
Document uses legible font sizes 99.77% 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
Keep request counts low and transfer sizes small 61 requests • 2,491 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid long main-thread tasks 18 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Efficiently encode images Potential savings of 171 KiB
Optimized images load faster and consume less cellular data

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
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not 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

city24.ee Alexa Rank

90,900

Global Rank

355

Norway
Traffic city24.ee Traffic
Search city24.ee Search

Domain Available

Domain (TDL) and Typo Status
city24.co Available Buy Now!
city24.us Available Buy Now!
city24.com Available Buy Now!
city24.org Available Buy Now!
city24.net Available Buy Now!
cty24.ee Available Buy Now!
dity24.ee Available Buy Now!
rity24.ee Available Buy Now!

Information Server city24.ee

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
server: nginx
date: Sun, 28 Mar 2021 19:09:11 GMT
content-type: text/html;charset=UTF-8
set-cookie: JSESSIONID=54400110D964185D9E155BBA38AF58D7; Path=/; Secure; HttpOnly
set-cookie: anonymousAuthCookie=16169585509614e72140e-d507-43dc-a8ae-9d6798d2e5bc; Expires=Fri, 15-Apr-2089 22:23:17 GMT; Path=/
pragma: no-cache
cache-control: no-cache, max-age=0, private, must-revalidate, no-store, max-age=0
content-language: et-EE
expires: Sun, 28 Mar 2021 19:09:10 GMT
vary: User-Agent,Accept-Encoding
content-encoding: gzip
set-cookie: BIGIP_COOKIE=!IztHntnlC7t28tAdUIq14wnHYPcGtwmdzZpAbdfRxuILGtEG6IBA4boZeVs95gvcyQiRHXax;Path=/
origin-id: 90.190.149.71
DNS Records DNS Resource Records associated with a hostname
city24.ee View DNS Records

Social Data

Delicious Total: 0
Facebook Total: 14,650
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0