2.8 sec in total
72 ms
2.3 sec
402 ms
Welcome to skyxe.ca homepage info - get ready to check Skyxe best content for Canada right away, or after learning these important things about skyxe.ca
Skyxe - Saskatoon International Airport
Visit skyxe.caWe analyzed Skyxe.ca page load time and found that the first response time was 72 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
skyxe.ca performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value7.9 s
3/100
25%
Value7.5 s
26/100
10%
Value710 ms
42/100
30%
Value0.154
75/100
15%
Value12.4 s
15/100
10%
72 ms
1173 ms
58 ms
25 ms
45 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Skyxe.ca, 76% (78 requests) were made to Yxe.ca and 11% (11 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Yxe.ca.
Page size can be reduced by 132.6 kB (16%)
806.1 kB
673.5 kB
In fact, the total size of Skyxe.ca main page is 806.1 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. 70% of websites need less resources to load. Images take 417.4 kB which makes up the majority of the site volume.
Potential reduce by 130.5 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 130.5 kB or 83% of the original size.
Potential reduce by 154 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. Skyxe images are well optimized though.
Potential reduce by 231 B
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 1.8 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. Skyxe.ca has all CSS files already compressed.
Number of requests can be reduced by 69 (78%)
89
20
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Skyxe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
skyxe.ca
72 ms
yxe.ca
1173 ms
js
58 ms
style.css
25 ms
custom.css
45 ms
horizBarChart.css
54 ms
material-charts.css
451 ms
style.min.css
42 ms
theme.min.css
86 ms
frontend-lite.min.css
48 ms
post-9.css
86 ms
elementor-icons.min.css
148 ms
swiper.min.css
87 ms
frontend-lite.min.css
88 ms
global.css
144 ms
post-3598.css
133 ms
post-14.css
135 ms
post-250.css
145 ms
default.css
134 ms
css
29 ms
fontawesome.min.css
135 ms
solid.min.css
147 ms
brands.min.css
152 ms
frontend-gtag.min.js
188 ms
breeze-prefetch-links.min.js
202 ms
jquery.min.js
197 ms
jquery-migrate.min.js
168 ms
jquery.horizBarChart.js
205 ms
material-charts.js
581 ms
widget-nav-menu.min.css
241 ms
widget-theme-elements.min.css
245 ms
widget-loop-builder.min.css
288 ms
widget-icon-list.min.css
227 ms
widgets.js
129 ms
email-decode.min.js
230 ms
language-switcher.min.css
252 ms
post-191.css
316 ms
regular.min.css
328 ms
hello-frontend.min.js
274 ms
jquery.smartmenus.min.js
297 ms
imagesloaded.min.js
355 ms
webpack-pro.runtime.min.js
304 ms
webpack.runtime.min.js
360 ms
frontend-modules.min.js
306 ms
wp-polyfill-inert.min.js
367 ms
regenerator-runtime.min.js
354 ms
wp-polyfill.min.js
340 ms
hooks.min.js
373 ms
i18n.min.js
341 ms
frontend.min.js
370 ms
waypoints.min.js
338 ms
core.min.js
314 ms
frontend.min.js
367 ms
elements-handlers.min.js
344 ms
update-logo.png
47 ms
seaarch-icon.png
104 ms
home-banner.jpg
103 ms
header-top-sadow.png
75 ms
arrive-icon.png
76 ms
arrive-icon-white.png
74 ms
departure-icon.png
155 ms
departures-white-icon.png
155 ms
car-icon.png
155 ms
time-icon.png
174 ms
catsa-icon.png
174 ms
more-arrow.png
174 ms
calender-icon.jpg
219 ms
time-icon.jpg
229 ms
pomo-code.jpg
221 ms
parking-img.jpg
220 ms
shpping-icon.png
219 ms
heading-arrow.png
220 ms
dinning-icon.png
261 ms
enter-icon.png
258 ms
service-icon.png
268 ms
airplan-icon.png
280 ms
twitter-bg-update.png
269 ms
twitter.png
259 ms
f-icon.png
283 ms
footer-twitter.png
272 ms
ins-icon.png
240 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
56 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
109 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
130 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
131 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
130 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
131 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
130 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
129 ms
fa-solid-900.woff
299 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
76 ms
settings
68 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
21 ms
yxe_ca
58 ms
polyfills-3b821eda8863adcc4a4b.js
24 ms
runtime-a697c5a1ae32bd7e4d42.js
45 ms
modules.20f98d7498a59035a762.js
86 ms
main-fd9ef5eb169057cda26d.js
96 ms
_app-88bf420a57d49e33be53.js
98 ms
%5BscreenName%5D-c33f0b02841cffc3e9b4.js
99 ms
_buildManifest.js
100 ms
_ssgManifest.js
101 ms
skyxe.ca accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
skyxe.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
skyxe.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
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 Skyxe.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 Skyxe.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.
skyxe.ca
Open Graph data is detected on the main page of Skyxe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: