7.1 sec in total
1 sec
5.8 sec
309 ms
Visit 220re.com now to see the best up-to-date 220 Re content and also check out these interesting facts you probably never knew about 220re.com
Visit 220re.comWe analyzed 220re.com page load time and found that the first response time was 1 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
220re.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value1.064
2/100
15%
Value0
0/100
10%
1037 ms
2252 ms
1808 ms
159 ms
369 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 55% of them (38 requests) were addressed to the original 220re.com, 12% (8 requests) were made to Apis.google.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain 220re.com.
Page size can be reduced by 695.8 kB (53%)
1.3 MB
620.9 kB
In fact, the total size of 220re.com main page is 1.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. 55% of websites need less resources to load. Images take 761.9 kB which makes up the majority of the site volume.
Potential reduce by 53.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 53.8 kB or 79% of the original size.
Potential reduce by 313.4 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. Obviously, 220 Re needs image optimization as it can save up to 313.4 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 119.6 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 119.6 kB or 62% of the original size.
Potential reduce by 209.1 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. 220re.com needs all CSS files to be minified and compressed as it can save up to 209.1 kB or 72% of the original size.
Number of requests can be reduced by 26 (41%)
63
37
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 220 Re. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
220re.com
1037 ms
www.220re.com
2252 ms
home.html
1808 ms
swfobject.js
159 ms
jquery-1.4.2.min.js
369 ms
check_form.js
169 ms
indexQuoteAnimation.js
169 ms
forms.js
234 ms
core.css
234 ms
product.css
252 ms
roundContainer.css
254 ms
colorData.css
313 ms
sidebarButtons.css
313 ms
home.css
326 ms
Loader_763323.js
139 ms
v1.js
111 ms
font-awesome.min.css
72 ms
sdk.js
189 ms
widgets.js
33 ms
platform.js
151 ms
page.js
51 ms
corporatebackground.jpg
353 ms
topleftshadow.png
220 ms
toprightshadow.png
357 ms
middlerightshadow.gif
216 ms
homepagepic.jpg
505 ms
find_needs.jpg
298 ms
homeBuyers.jpg
300 ms
homeSellers.jpg
382 ms
mortgageMarketplace.jpg
382 ms
174 ms
xd_arbiter.php
123 ms
xd_arbiter.php
255 ms
quote_head.jpg
141 ms
quickquotegradient.jpg
213 ms
quickquotepopup.gif
142 ms
quotemebutton.png
142 ms
lock.png
167 ms
re_market_header.jpg
175 ms
c5.jpg
272 ms
homesearch.png
249 ms
featured.png
249 ms
dream.png
435 ms
value.png
383 ms
sidebarButton.jpg
275 ms
bottomleftshadow.png
530 ms
bottomrightshadow.png
531 ms
eho_footer.jpg
346 ms
1TF2XTZ
73 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
76 ms
sm13.html
91 ms
cb=gapi.loaded_0
67 ms
cb=gapi.loaded_1
101 ms
fastbutton
132 ms
1px.png
33 ms
icons.15.svg.css
85 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
27 ms
ga.js
88 ms
postmessageRelay
78 ms
cb=gapi.loaded_0
40 ms
cb=gapi.loaded_1
39 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
98 ms
like.php
157 ms
jot
86 ms
3193398744-postmessagerelay.js
49 ms
rpc:shindig_random.js
52 ms
cb=gapi.loaded_0
11 ms
qeKvIRsJabD.js
297 ms
LVx-xkvaJ0b.png
333 ms
220re.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
220re.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
220re.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
N/A
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 220re.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that 220re.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
220re.com
Open Graph description is not detected on the main page of 220 Re. 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: