1.6 sec in total
47 ms
1.2 sec
332 ms
Visit expo.ca now to see the best up-to-date Expo content and also check out these interesting facts you probably never knew about expo.ca
Expographiq designs and builds museum exhibitions, trade show booths, visitor centres, donor walls and branded spaces.
Visit expo.caWe analyzed Expo.ca page load time and found that the first response time was 47 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
expo.ca performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value14.3 s
0/100
25%
Value6.6 s
38/100
10%
Value840 ms
34/100
30%
Value0.341
33/100
15%
Value10.2 s
25/100
10%
47 ms
107 ms
70 ms
72 ms
69 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Expo.ca, 76% (45 requests) were made to U4s4x8b2.stackpathcdn.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (241 ms) relates to the external source Sc.lfeeder.com.
Page size can be reduced by 233.8 kB (13%)
1.8 MB
1.6 MB
In fact, the total size of Expo.ca main page is 1.8 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 38.9 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 5.5 kB, which is 11% 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 38.9 kB or 78% of the original size.
Potential reduce by 92.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. Expo images are well optimized though.
Potential reduce by 102.2 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 102.2 kB or 47% of the original size.
Potential reduce by 181 B
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. Expo.ca needs all CSS files to be minified and compressed as it can save up to 181 B or 14% of the original size.
Number of requests can be reduced by 30 (54%)
56
26
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Expo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
expo.ca
47 ms
www.expo.ca
107 ms
normalize.css
70 ms
style.css
72 ms
modernizr-2.6.2.min.js
69 ms
jquery.min.js
94 ms
cufon.js
66 ms
Helvetica_Neue_LT_Std_400-Helvetica_Neue_LT_Std_750.font.js
70 ms
jquery.mobile.custom.min.js
114 ms
jquery.fancybox.css
118 ms
jquery.fancybox.pack.js
119 ms
tinynav.min.js
120 ms
jquery.cycle2.min.js
123 ms
jquery.cycle2.carousel.min.js
123 ms
jquery.cycle2.swipe.min.js
128 ms
jquery.hoverIntent.minified.js
122 ms
ugl-site-code.js
128 ms
style.min.css
126 ms
styles.css
135 ms
style.min.css
137 ms
script.min.js
133 ms
jquery.min.js
135 ms
jquery-migrate.min.js
135 ms
external-tracking.min.js
134 ms
classic-10_7.css
117 ms
mc-validate.js
117 ms
index.js
222 ms
index.js
222 ms
lftracker_v1_DzLR5a5Jo5A8BoQ2.js
241 ms
tracking.min.js
180 ms
analytics.js
188 ms
bg-top-header-pattern.png
98 ms
icon-search.png
97 ms
icon-submit-files.png
96 ms
img-logo.png
97 ms
expographiq-home-museums-gros-morne-banner.jpg
146 ms
img-home-section-arrow.png
97 ms
expographiq-home-niagara-falls-museums-thumbs.jpg
108 ms
expographiq-home-climate-change-conference-exhibits-thumbs1.jpg
120 ms
expographiq-home-air-canada-custom-thumbs.jpg
108 ms
expographiq-home-volkswagen-3d-marketing-thumbs.jpg
107 ms
img-quote-left.png
102 ms
img-quote-right.png
105 ms
img-testimonial-arrow-left.png
224 ms
img-testimonial-arrow-right.png
143 ms
img-footer-icon-museums.png
144 ms
img-footer-icon-exhibits.png
144 ms
img-footer-icon-exhibits-12.png
147 ms
img-footer-icon-exhibits-13.png
145 ms
btn-footer-linkedin-v2.png
146 ms
open
91 ms
open
92 ms
collect
10 ms
collect
44 ms
collect
19 ms
tr.lfeeder.com
79 ms
max-480.css
7 ms
481-768.css
10 ms
min-769.css
9 ms
expo.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
<input type="image"> elements do not have [alt] text
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.
expo.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
expo.ca SEO score
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 Expo.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 Expo.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.
expo.ca
Open Graph description is not detected on the main page of Expo. 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: