8.6 sec in total
3.2 sec
5.2 sec
201 ms
Click here to check amazing Franklee content. Otherwise, check out these important facts you probably never knew about franklee.ca
(description)
Visit franklee.caWe analyzed Franklee.ca page load time and found that the first response time was 3.2 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
franklee.ca performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value1.6 s
99/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.8 s
100/100
10%
3218 ms
1512 ms
1585 ms
1793 ms
1535 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 32% of them (20 requests) were addressed to the original Franklee.ca, 19% (12 requests) were made to Imambo.com and 18% (11 requests) were made to Webcms.dominionintranet.ca. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Franklee.ca.
Page size can be reduced by 405.8 kB (47%)
864.8 kB
458.9 kB
In fact, the total size of Franklee.ca main page is 864.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 492.6 kB which makes up the majority of the site volume.
Potential reduce by 43.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. 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 43.0 kB or 69% of the original size.
Potential reduce by 11.8 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. Franklee images are well optimized though.
Potential reduce by 319.7 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 319.7 kB or 65% of the original size.
Potential reduce by 31.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. Franklee.ca needs all CSS files to be minified and compressed as it can save up to 31.4 kB or 56% of the original size.
Number of requests can be reduced by 26 (43%)
61
35
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Franklee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
franklee.ca
3218 ms
reset.css
1512 ms
screen.css
1585 ms
jquery-1.7.2.min.js
1793 ms
jquery.wad.js
1535 ms
viddler.js
1657 ms
form.css
1582 ms
wufoo.js
1584 ms
pop.js
1608 ms
colorbox.css
1715 ms
jquery.colorbox-min.js
1834 ms
addthis_widget.js
11 ms
bgBody.png
77 ms
s13108_1368639487.jpg
682 ms
vid1.jpg
679 ms
bgHeader.png
100 ms
bgHeaderPhoto.png
100 ms
img_header.jpg
222 ms
bgContent.png
100 ms
sideHeading.png
100 ms
sideBoxApply1.jpg
142 ms
btn_eng.jpg
219 ms
btn_chi.jpg
219 ms
vid2.jpg
677 ms
vid3.jpg
674 ms
vid4.jpg
690 ms
vid5.jpg
690 ms
vid6.jpg
691 ms
vid7.jpg
690 ms
vid8.jpg
745 ms
vid9.jpg
753 ms
buttonHomePrev.png
848 ms
buttonHomeNext.png
845 ms
index.htm
241 ms
40 ms
homeVideoThumbGrey.png
85 ms
bgFooter.png
79 ms
overlay.png
75 ms
300lo.json
50 ms
border.png
75 ms
controls.png
128 ms
embed.css
64 ms
sh.8e5f85691f9aaa082472a194.html
33 ms
n99h
14 ms
p0dg
13 ms
thumbnail_2_a71faae3_v1.jpg
135 ms
greyleatherbg.jpg
1216 ms
index_01.png
381 ms
index_02.png
130 ms
logo.jpg
382 ms
button.jpg
131 ms
index_04.png
131 ms
index_05.png
382 ms
index_06.png
380 ms
index_07.png
383 ms
spacer.gif
380 ms
embed.html
31 ms
main-built.js
111 ms
viddler.css
30 ms
viddler.videos.getPlaybackDetails.json
47 ms
ajax-loader.gif
34 ms
index_05-over.png
128 ms
franklee.ca 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.
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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
franklee.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
franklee.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Franklee.ca 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 Franklee.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.
franklee.ca
Open Graph description is not detected on the main page of Franklee. 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: