3.7 sec in total
772 ms
2.5 sec
394 ms
Visit broughton.ca now to see the best up-to-date Broughton content and also check out these interesting facts you probably never knew about broughton.ca
Bob Broughton's personal web site
Visit broughton.caWe analyzed Broughton.ca page load time and found that the first response time was 772 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
broughton.ca performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value7.4 s
4/100
25%
Value7.9 s
23/100
10%
Value7,040 ms
0/100
30%
Value0.045
99/100
15%
Value20.1 s
2/100
10%
772 ms
176 ms
341 ms
250 ms
251 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 60% of them (43 requests) were addressed to the original Broughton.ca, 18% (13 requests) were made to Apis.google.com and 8% (6 requests) were made to Linkedin.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Broughton.ca.
Page size can be reduced by 437.9 kB (40%)
1.1 MB
664.2 kB
In fact, the total size of Broughton.ca main page is 1.1 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. 50% of websites need less resources to load. Images take 519.0 kB which makes up the majority of the site volume.
Potential reduce by 93.1 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 93.1 kB or 90% of the original size.
Potential reduce by 10.6 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. Broughton images are well optimized though.
Potential reduce by 324.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 324.5 kB or 69% of the original size.
Potential reduce by 9.7 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. Broughton.ca needs all CSS files to be minified and compressed as it can save up to 9.7 kB or 83% of the original size.
Number of requests can be reduced by 43 (63%)
68
25
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Broughton. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
broughton.ca
772 ms
style.css
176 ms
jquery.min.js
341 ms
jquery-noconflict.js
250 ms
jquery-migrate.min.js
251 ms
caption.js
255 ms
bootstrap.min.js
253 ms
mootools-core.js
408 ms
core.js
406 ms
mootools-more.js
638 ms
template_css.css
435 ms
plusone.js
59 ms
in.js
6 ms
button.js
14 ms
hm-ppc-banners-dynamic-488x160.png
460 ms
spacer.gif
311 ms
cornerleft.png
162 ms
top.png
310 ms
cornerright.png
160 ms
header.png
518 ms
headerright.png
316 ms
barleft.png
335 ms
barleftmod.png
333 ms
barmid.png
408 ms
barrightmod.png
407 ms
barright.png
428 ms
edgeleft.png
482 ms
moduleheader.png
482 ms
arrow.png
559 ms
gplus-64.png
584 ms
find-us-on-facebook_logo.jpg
586 ms
printButton.png
634 ms
emailButton.png
636 ms
normal_diego_bob_2~0.jpg
702 ms
tc_comments_screenshot.jpg
793 ms
mod_thiscategory-350.jpg
812 ms
normal_WCWC_2008_agm_2a.jpg
807 ms
vt_yellow_ribbon.jpg
779 ms
nwtc_logo.jpg
781 ms
court_1.jpg
923 ms
studleft.png
923 ms
studright.png
925 ms
footer.png
936 ms
bottleft.png
948 ms
bottom.png
956 ms
bottright.png
1065 ms
cb=gapi.loaded_0
147 ms
secureAnonymousFramework
41 ms
cb=gapi.loaded_1
134 ms
fastbutton
279 ms
fastbutton
275 ms
fastbutton
265 ms
fastbutton
258 ms
fastbutton
250 ms
share
230 ms
sprite_connect_v14.png
231 ms
share
233 ms
share
248 ms
share
275 ms
share
243 ms
share
236 ms
fastbutton
180 ms
edgeright.png
935 ms
meter.asp
112 ms
postmessageRelay
176 ms
meter.asp
85 ms
cb=gapi.loaded_0
70 ms
cb=gapi.loaded_1
67 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
48 ms
3193398744-postmessagerelay.js
30 ms
rpc:shindig_random.js
47 ms
cb=gapi.loaded_0
10 ms
broughton.ca accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
broughton.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
broughton.ca 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
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Broughton.ca 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 Broughton.ca 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.
broughton.ca
Open Graph description is not detected on the main page of Broughton. 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: