801 ms in total
85 ms
429 ms
287 ms
Welcome to century21.com homepage info - get ready to check CENTURY 21 best content for United States right away, or after learning these important things about century21.com
Visit century21.comWe analyzed Century21.com page load time and found that the first response time was 85 ms and then it took 716 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
century21.com performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value27.5 s
0/100
25%
Value7.5 s
26/100
10%
Value1,360 ms
16/100
30%
Value0.005
100/100
15%
Value15.3 s
7/100
10%
85 ms
61 ms
7 ms
11 ms
31 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 64% of them (34 requests) were addressed to the original Century21.com, 6% (3 requests) were made to My.century21.com and 4% (2 requests) were made to Chat.xtdirect.com. The less responsive or slowest element that took the longest time to load (154 ms) relates to the external source Chat.xtdirect.com.
Page size can be reduced by 1.4 MB (43%)
3.3 MB
1.9 MB
In fact, the total size of Century21.com main page is 3.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 40.9 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 8.1 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 40.9 kB or 83% of the original size.
Potential reduce by 36.5 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. CENTURY 21 images are well optimized though.
Potential reduce by 633.2 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 633.2 kB or 70% of the original size.
Potential reduce by 679.4 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Century21.com needs all CSS files to be minified and compressed as it can save up to 679.4 kB or 84% of the original size.
Number of requests can be reduced by 28 (58%)
48
20
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CENTURY 21. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
century21.com
85 ms
www.century21.com
61 ms
advanceCSS.css
7 ms
homepageonly.css
11 ms
conversion_async.js
31 ms
ScriptProvider.php
154 ms
defaultJS.js
12 ms
la.js
28 ms
dynamic.js
95 ms
defaultCSS.css
12 ms
dynamic.css
5 ms
ga.js
53 ms
beacon.js
52 ms
c21-backgrounds21.jpg
62 ms
texturesheet.png
60 ms
callicon.png
59 ms
searchbox-collapsed.png
59 ms
clear.gif
60 ms
searchbox-expanded-results-1px-width.png
59 ms
searchbox-expanded-results-top.png
61 ms
searchbox-expanded-results-bottom.png
61 ms
heroframebg.png
62 ms
jdpower_bg.jpg
70 ms
texturesheet.png
63 ms
mortgagehero.png
63 ms
mortgageherotitle.png
63 ms
herolink.png
63 ms
quizhero.png
64 ms
personalitytitle.png
64 ms
pagefooterbg.png
64 ms
footer-haze.png
64 ms
social-facebook-icon.png
64 ms
social-twitter-icon.png
65 ms
social-gplus-icon.png
66 ms
social-instagram-icon.png
66 ms
social-youtube-icon.png
67 ms
__utm.gif
71 ms
activityi;src=915635;type=cnncent;cat=homepage;ord=1;num=556443857494.7417
72 ms
iframe.proxy.html
34 ms
c21-mainsearchbar-clearbutton.png
9 ms
collect
67 ms
ScriptProviderReal.php
105 ms
layoutPrint.css
2 ms
_phonePortal.css
19 ms
tre
26 ms
lb
22 ms
jquery-1.7.1.js
93 ms
_tabletPortal.css
4 ms
LightningBolt.html
42 ms
53 ms
LightningBolt.js
23 ms
44 ms
utag.js
11 ms
century21.com accessibility score
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
century21.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
century21.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Century21.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Century21.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
century21.com
Open Graph description is not detected on the main page of CENTURY 21. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: