3.6 sec in total
138 ms
2 sec
1.4 sec
Visit jexplore.ca now to see the best up-to-date Jex PLO Re content for Canada and also check out these interesting facts you probably never knew about jexplore.ca
Apprenez à parler français ou anglais, ou trouvez un emploi de moniteur d’ALS, de FLS ou de FLP dans le cadre des Programmes de langues officielles, financés par le gouvernement du Canada. En savoir p...
Visit jexplore.caWe analyzed Jexplore.ca page load time and found that the first response time was 138 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
jexplore.ca performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value34.1 s
0/100
25%
Value25.1 s
0/100
10%
Value3,850 ms
1/100
30%
Value0.532
14/100
15%
Value32.6 s
0/100
10%
138 ms
171 ms
179 ms
101 ms
100 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jexplore.ca, 65% (112 requests) were made to Francaisanglais.ca and 13% (23 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (676 ms) relates to the external source Francaisanglais.ca.
Page size can be reduced by 215.7 kB (4%)
5.0 MB
4.8 MB
In fact, the total size of Jexplore.ca main page is 5.0 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. Only a small number of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 189.2 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 189.2 kB or 80% of the original size.
Potential reduce by 186 B
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. Jex PLO Re images are well optimized though.
Potential reduce by 5.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 20.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. Jexplore.ca has all CSS files already compressed.
Number of requests can be reduced by 114 (81%)
140
26
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jex PLO Re. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 42 to 1 for CSS and as a result speed up the page load time.
jexplore.ca
138 ms
francaisanglais.ca
171 ms
gtm.js
179 ms
events.js
101 ms
fbevents.js
100 ms
js
271 ms
js
349 ms
hotjar-2540317.js
177 ms
events.js
149 ms
core.js
151 ms
decisionMobileMapV2.css
67 ms
wp-notification-bars-public.css
82 ms
style.min.css
83 ms
styles.css
87 ms
cmec-interactive-map-public.css
90 ms
cmec_training_sessions-public.css
147 ms
styles.css
144 ms
style.min.css
264 ms
Banner.css
146 ms
LogIn.css
145 ms
be.css
147 ms
animations.min.css
238 ms
fontawesome.css
231 ms
jplayer.blue.monday.min.css
235 ms
responsive.css
239 ms
css
139 ms
js_composer.min.css
244 ms
ubermenu.min.css
324 ms
minimal.css
332 ms
all.min.css
327 ms
style.css
325 ms
css2
224 ms
css2
324 ms
Footer.css
325 ms
ContactForm.css
312 ms
Header.css
498 ms
custom-style.css
501 ms
font-awesome.min.css
128 ms
choices.min.css
496 ms
css2
321 ms
CustomTabs.css
496 ms
jquery.min.js
499 ms
jquery-migrate.min.js
493 ms
mobileProvinceSelect.js
531 ms
language-cookie.js
655 ms
popup.js
530 ms
cmec-interactive-map-public.js
650 ms
cmec_training_sessions-public.js
652 ms
wp-notification-bars-public.js
652 ms
jquery.bind-first-0.2.3.min.js
654 ms
swiper-bundle.min.css
121 ms
video-js.css
121 ms
swiper-bundle.min.js
209 ms
up_loader.1.1.0.js
220 ms
sharer.min.js
236 ms
api.js
215 ms
sidebar.css
674 ms
social_icons.css
642 ms
swiperBanner.css
624 ms
HomeDescription.css
617 ms
ImageInfoBoxNew.css
618 ms
CMECButton.css
615 ms
DownloadApp.css
560 ms
HomeFAQ.css
586 ms
js.cookie-2.1.3.min.js
578 ms
public.js
597 ms
xdomain-data.js
563 ms
modules.305879d9d5e96288a7f4.js
352 ms
js
121 ms
loader.js
325 ms
destination
324 ms
js
288 ms
js
318 ms
Header.js
495 ms
choices.min.js
489 ms
ContactForm.js
499 ms
LazyLoad.js
509 ms
LazyLoadInit.js
495 ms
fitty.min.js
468 ms
js
243 ms
analytics.js
237 ms
ListCorrector.js
427 ms
nicefileinput.min.js
428 ms
TestimonalTextSwitch.js
437 ms
index.js
427 ms
index.js
430 ms
core.min.js
483 ms
tabs.min.js
312 ms
debouncedresize.min.js
283 ms
magnificpopup.min.js
309 ms
menu.js
310 ms
css2
159 ms
visible.min.js
308 ms
animations.min.js
281 ms
jplayer.min.js
279 ms
call-tracking_9.js
136 ms
collect
50 ms
enllax.min.js
161 ms
translate3d.js
157 ms
scripts.js
200 ms
new-tab.js
157 ms
ubermenu.min.js
158 ms
sidebar.js
133 ms
akismet-frontend.js
174 ms
js_composer_front.min.js
172 ms
collect
14 ms
wcm
13 ms
facebook.png
84 ms
facebookhover.png
85 ms
twitter.png
94 ms
twitter_purplehiover.png
93 ms
cmec_o_logo_colour_WHT.png
88 ms
cmec_o_logo_colour_WHT@2x-1.png
93 ms
cmec_o_logo_colour_WHT-2.png
146 ms
OLP-FR-RGB-HORIZ-1.svg
89 ms
new-explore-menu.svg
98 ms
new-explore-menu-2.svg
94 ms
new-odyssey-menu.svg
95 ms
fr.png
98 ms
en.png
145 ms
CMEC_banner_landingpage.png
147 ms
experiences_banner.png
154 ms
destinstion_clic.png
150 ms
explore.png
155 ms
OLP-PLO-Website-Main-Page-image-min-1-scaled.jpg
663 ms
cmec_home_image_plus.png
151 ms
cmec_home_image_square.png
156 ms
cmec_home_image_diomond.png
129 ms
rasheed-kemy-oqY09oVTa3k-unsplash-1.png
518 ms
Google-Play_Badge_FR.png
146 ms
App_Store_Badge_FR.png
195 ms
Polygon-2-1.svg
193 ms
Polygon-2.svg
192 ms
PLO_OL_1-2-1.svg
593 ms
PLO_OL_1-1.svg
599 ms
PLO_OL_1-3-1.svg
614 ms
OLP-logo-with-White-BG-1.svg
605 ms
Canada_wordmark-2.png
627 ms
CMEC_logo_fre-eng_4c_new-colour.png
623 ms
new_magnifying.svg
676 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
518 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
529 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
526 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
529 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
529 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
528 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
529 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
531 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
531 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
532 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
531 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
544 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
543 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
548 ms
fa-solid-900.woff
638 ms
fa-solid-900.woff
639 ms
fa-regular-400.woff
636 ms
fa-regular-400.woff
638 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshRTM.ttf
547 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhRTM.ttf
549 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDshRTM.ttf
549 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmRTM.ttf
549 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmRTM.ttf
549 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmRTM.ttf
551 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDBImRTM.ttf
551 ms
JTUSjIg69CK48gW7PXooxW4.ttf
550 ms
JTUSjIg69CK48gW7PXoo9Wlhzg.ttf
549 ms
events.js
490 ms
bullet_cmec.png
527 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
19 ms
recaptcha__fr.js
140 ms
jexplore.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.
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
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.
jexplore.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
jexplore.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jexplore.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Jexplore.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.
jexplore.ca
Open Graph description is not detected on the main page of Jex PLO Re. 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: