2.7 sec in total
329 ms
846 ms
1.5 sec
Click here to check amazing BRANDON DONNELLY content for United States. Otherwise, check out these important facts you probably never knew about brandondonnelly.com
I'm a real estate developer based in Toronto. This is my daily blog for city builders. Join over 15,000 followers and subscribers. Daily email at 6AM (ET).
Visit brandondonnelly.comWe analyzed Brandondonnelly.com page load time and found that the first response time was 329 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
brandondonnelly.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value3.5 s
65/100
25%
Value11.9 s
4/100
10%
Value2,680 ms
4/100
30%
Value0.049
99/100
15%
Value20.8 s
2/100
10%
329 ms
14 ms
4 ms
10 ms
401 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Brandondonnelly.com, 24% (13 requests) were made to 40.media.tumblr.com and 16% (9 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (464 ms) relates to the external source 40.media.tumblr.com.
Page size can be reduced by 623.3 kB (15%)
4.2 MB
3.5 MB
In fact, the total size of Brandondonnelly.com main page is 4.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 85.0 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 22.4 kB, which is 21% 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 85.0 kB or 80% of the original size.
Potential reduce by 163.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. BRANDON DONNELLY images are well optimized though.
Potential reduce by 352.5 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 352.5 kB or 64% of the original size.
Potential reduce by 22.3 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. Brandondonnelly.com needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 76% of the original size.
Number of requests can be reduced by 17 (33%)
52
35
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BRANDON DONNELLY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
brandondonnelly.com
329 ms
pre_tumblelog.js
14 ms
font-awesome.min.css
4 ms
main2.0.min.css
10 ms
load.sumome.com
401 ms
tumblelog_post_message_queue.js
11 ms
stylesheet.css
27 ms
embed.js
130 ms
jquery.min.js
39 ms
photosetgrid1.0.1.js
38 ms
index.js
39 ms
analytics.js
23 ms
tumblr_inline_o48w5lCgjZ1r97ndl_540.jpg
212 ms
tumblr_inline_o48wb7LOc21r97ndl_540.jpg
23 ms
tumblr_inline_o48wbbNvhJ1r97ndl_540.jpg
269 ms
tumblr_inline_o48wbfVCRv1r97ndl_540.jpg
297 ms
tumblr_inline_o48wbiHLFE1r97ndl_540.jpg
422 ms
tumblr_static_4l2mqqh3w2ecgcwc8008kckso.png
21 ms
count.js
52 ms
like_iframe.html
43 ms
327c4b0300e908df58c231318884e0c2
196 ms
tumblr_inline_o3wfsgBWWe1r97ndl_540.png
44 ms
tumblr_inline_o46om4VPlb1r97ndl_540.png
357 ms
tumblr_inline_o3wfb6Ctqe1r97ndl_540.png
251 ms
tumblr_inline_o3wfdwqYG71r97ndl_540.png
318 ms
tumblr_inline_o3wfn4kNvD1r97ndl_540.png
359 ms
tumblr_inline_o3wg01KOnI1r97ndl_540.png
318 ms
tumblr_inline_o3wfwhdGUX1r97ndl_540.png
410 ms
tumblr_inline_o3wfusBYjj1r97ndl_540.png
413 ms
tumblr_inline_o3sliu6izy1r97ndl_540.png
464 ms
tumblr_inline_o3slinNbIR1r97ndl_540.png
416 ms
tumblr_inline_o43uccVIqI1r97ndl_540.jpg
37 ms
tumblr_inline_o40aqrsH301r97ndl_540.png
39 ms
tumblr_inline_o3wfy3ofaC1r97ndl_540.png
40 ms
tumblr_inline_o3wfly0ITB1r97ndl_540.png
38 ms
tumblr_inline_o3wfotqThH1r97ndl_540.png
36 ms
tumblr_inline_o3wfqdiWiN1r97ndl_540.png
37 ms
collect
18 ms
fontawesome-webfont.woff
5 ms
count-data.js
45 ms
collect
148 ms
embed.js
219 ms
impixu
96 ms
impixu
33 ms
count-data.js
59 ms
analytics.html
42 ms
login_check.html
17 ms
rapid-3.36.js
36 ms
rapidworker-1.2.js
34 ms
ga.js
101 ms
analytics.js
60 ms
cs.js
111 ms
yql
191 ms
__utm.gif
17 ms
cedexis.radar.js
13 ms
brandondonnelly.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
brandondonnelly.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
Issues were logged in the Issues panel in Chrome Devtools
brandondonnelly.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 Brandondonnelly.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 Brandondonnelly.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.
brandondonnelly.com
Open Graph data is detected on the main page of BRANDON DONNELLY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: