2.6 sec in total
184 ms
2.2 sec
243 ms
Visit graham.ca now to see the best up-to-date Graham content for Canada and also check out these interesting facts you probably never knew about graham.ca
Visit graham.caWe analyzed Graham.ca page load time and found that the first response time was 184 ms and then it took 2.5 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.
graham.ca performance score
184 ms
34 ms
86 ms
210 ms
74 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 54% of them (70 requests) were addressed to the original Graham.ca, 5% (7 requests) were made to Px.owneriq.net and 5% (6 requests) were made to Dsum-sec.casalemedia.com. The less responsive or slowest element that took the longest time to load (488 ms) belongs to the original domain Graham.ca.
Page size can be reduced by 3.2 MB (62%)
5.1 MB
1.9 MB
In fact, the total size of Graham.ca main page is 5.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. 80% 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. CSS take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 260.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 260.3 kB or 90% of the original size.
Potential reduce by 6.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. Graham images are well optimized though.
Potential reduce by 961.0 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 961.0 kB or 74% of the original size.
Potential reduce by 1.9 MB
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. Graham.ca needs all CSS files to be minified and compressed as it can save up to 1.9 MB or 87% of the original size.
Number of requests can be reduced by 88 (81%)
109
21
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Graham. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
graham.ca
184 ms
shareaholic.js
34 ms
wp-emoji-release.min.js
86 ms
ai1ec_parsed_css.css
210 ms
styles.css
74 ms
layerslider.css
77 ms
layerslider.custom.css
75 ms
css
25 ms
style.css
77 ms
css
37 ms
js_composer.css
226 ms
main.css
160 ms
style.css
123 ms
font-awesome.css
135 ms
required.css
140 ms
responsive.css
176 ms
admin_style.min.css
173 ms
js_composer.min.css
302 ms
jquery.js
276 ms
jquery-migrate.min.js
274 ms
greensock.js
278 ms
layerslider.kreaturamedia.jquery.js
278 ms
layerslider.transitions.js
276 ms
jquery.carouFredSel-6.2.1.js
327 ms
prettyPhoto.css
325 ms
owl.carousel.css
295 ms
owl.theme.default.css
324 ms
animate.min.css
332 ms
plugin.css
333 ms
jquery.form.min.js
335 ms
scripts.js
341 ms
yuzo-postviews-cache.js
341 ms
jquery.equalizer.js
343 ms
main.js
368 ms
jquery.cookie.js
368 ms
custom.js
372 ms
jquery.sonar.min.js
377 ms
lazy-load.js
379 ms
js_composer_front.js
394 ms
core.min.js
403 ms
1bb4b6ff13cf87ebf51e831a49aa666b.json
208 ms
widget.min.js
349 ms
accordion.min.js
349 ms
jquery.prettyPhoto.js
374 ms
owl.carousel.js
488 ms
imagesloaded.pkgd.min.js
366 ms
tom.css
335 ms
underscore.min.js
419 ms
waypoints.min.js
419 ms
vc_grid_style_all.js
400 ms
vc_grid_style_load_more.js
390 ms
vc_grid_style_lazy.js
397 ms
vc_grid_style_pagination.js
351 ms
vc_grid.js
300 ms
responsiveslides.min.js
298 ms
analytics.js
43 ms
logo-graham.png
68 ms
1x1.trans.gif
69 ms
Screen-Shot-2015-10-09-at-4.27.25-PM.png
165 ms
collect
16 ms
shrMain.min.js
55 ms
RobotoSlab-Light.ttf
221 ms
Oswald-Regular.otf
220 ms
fontawesome-webfont.woff
220 ms
skin.css
104 ms
admin-ajax.php
303 ms
admin-ajax.php
457 ms
admin-ajax.php
423 ms
twitter_feed_icons_sprite.png
87 ms
jquery.min.js
71 ms
St.-Patricks-Bridge-Calgary.png
87 ms
slider-4-1024x588.png
178 ms
GrahamImages_Retina3.jpg
175 ms
GrahamImages_Retina1.jpg
177 ms
pageview.gif
89 ms
blank.gif
67 ms
skin.png
49 ms
vglnk.js
14 ms
partners.js
58 ms
pixel.gif
14 ms
pixel.gif
14 ms
sholic.js
121 ms
usermatch
234 ms
beacon.js
118 ms
wpe-common.css
95 ms
Port-Dover-3-1024x677.jpg
144 ms
Military-Police-Acadmey-2-1024x507.jpg
139 ms
cms-sh2c.html
78 ms
ping_match.gif
39 ms
eexelate.js
51 ms
53 ms
2964
22 ms
pixel
38 ms
ep
9 ms
ep
16 ms
pixel
21 ms
57 ms
pixel
16 ms
pixel
18 ms
usermatch
138 ms
match-result
49 ms
cm
25 ms
rs
27 ms
net.php
9 ms
pixel
19 ms
generic
7 ms
generic
5 ms
xrefid.xgi
5 ms
ermcm
11 ms
pxj
12 ms
pixel.gif
8 ms
pixel.gif
20 ms
gr
81 ms
Vut4q8AoJTYAAbYY2PQAAADS%26595
133 ms
casale
67 ms
218 ms
GenericUserSync.ashx
79 ms
i.gif
233 ms
xrefid.xgi
31 ms
crum
228 ms
pixel
55 ms
rum
246 ms
rum
282 ms
rum
277 ms
ping
63 ms
m
109 ms
rum
183 ms
domains
57 ms
crum
165 ms
graham.ca SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Graham.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 Graham.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.
graham.ca
Open Graph description is not detected on the main page of Graham. 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: