4.2 sec in total
244 ms
2.7 sec
1.3 sec
Click here to check amazing Move Smartly content for Canada. Otherwise, check out these important facts you probably never knew about movesmartly.com
Original, data-driven analysis and insights into Toronto real estate market - Realosophy's John Pasalis and other expert views on real estate market, data, mortgage, policy, finance, and law.
Visit movesmartly.comWe analyzed Movesmartly.com page load time and found that the first response time was 244 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
movesmartly.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value9.3 s
1/100
25%
Value6.2 s
43/100
10%
Value300 ms
79/100
30%
Value0
100/100
15%
Value15.0 s
7/100
10%
244 ms
173 ms
14 ms
68 ms
8 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Movesmartly.com, 27% (13 requests) were made to Realosophy.typepad.com and 14% (7 requests) were made to Static.typepad.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Docs.google.com.
Page size can be reduced by 373.5 kB (25%)
1.5 MB
1.1 MB
In fact, the total size of Movesmartly.com main page is 1.5 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. 45% of websites need less resources to load. Images take 999.3 kB which makes up the majority of the site volume.
Potential reduce by 71.3 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 71.3 kB or 79% of the original size.
Potential reduce by 30.3 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. Move Smartly images are well optimized though.
Potential reduce by 223.4 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 223.4 kB or 64% of the original size.
Potential reduce by 48.5 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. Movesmartly.com needs all CSS files to be minified and compressed as it can save up to 48.5 kB or 82% of the original size.
Number of requests can be reduced by 18 (42%)
43
25
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Move Smartly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.movesmartly.com
244 ms
styles.css
173 ms
flyouts-min.js
14 ms
recommend.js
68 ms
all.js
8 ms
print.css
168 ms
brand
14 ms
sttypepad2.js
5 ms
quant.js
6 ms
brand
37 ms
base-weblog.css
236 ms
bxslider.css
163 ms
widgets.css
164 ms
recentpostsfancy.css
156 ms
tipjar.css
85 ms
analytics.js
17 ms
6a00d83420cedf53ef01bb08cad016970d-800wi
323 ms
feed-icon32x32.png
50 ms
oimg
398 ms
6a00d83420cedf53ef01b8d1acefcf970c-800wi
310 ms
6a00d83420cedf53ef01b7c81ce2ce970b-800wi
401 ms
6a00d83420cedf53ef01bb08c1a1d5970d-800wi
256 ms
6a00d83420cedf53ef01b8d089913c970c-800wi
396 ms
6a00d83420cedf53ef01b8d1a7e62d970c-800wi
537 ms
6a00d83420cedf53ef01b7c81cde25970b-800wi
870 ms
6a00d83420cedf53ef01b7c81a66e0970b-800wi
467 ms
6a00d83420cedf53ef01bb08be7937970d-800wi
706 ms
RealosophyLogoSmall.jpg
399 ms
TwitterIcon2.png
662 ms
oimg
546 ms
oimg
550 ms
oimg
552 ms
sdk.js
42 ms
6a00d83420cedf53ef0120a78e315d970b-pi
550 ms
header.png
467 ms
collect
20 ms
google_custom_search_watermark.gif
63 ms
ga.js
12 ms
__utm.gif
25 ms
jquery-1.4.2.min.js
5 ms
stats
159 ms
pixel;r=93769696;a=p-fcYWUmj5YbYKM;tags=typepad.extended;fpan=1;fpa=P0-1342643516-1458492221251;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458492221251;tzo=-180;ref=;url=http%3A%2F%2Fwww.movesmartly.com%2F;ogl=
21 ms
beacon.js
22 ms
buttons.js
8 ms
oimg
750 ms
oimg
613 ms
oimg
834 ms
oimg
1208 ms
getAllAppDefault.esi
97 ms
movesmartly.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
movesmartly.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
movesmartly.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Movesmartly.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Movesmartly.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.
movesmartly.com
Open Graph description is not detected on the main page of Move Smartly. 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: