2.9 sec in total
66 ms
1.7 sec
1.1 sec
Click here to check amazing St U content for Canada. Otherwise, check out these important facts you probably never knew about stu.ca
St. Thomas University - Fredericton, NB Canada
Visit stu.caWe analyzed Stu.ca page load time and found that the first response time was 66 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
stu.ca performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value72.5 s
0/100
25%
Value19.7 s
0/100
10%
Value2,630 ms
4/100
30%
Value0.008
100/100
15%
Value34.3 s
0/100
10%
66 ms
144 ms
35 ms
30 ms
103 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 41% of them (32 requests) were addressed to the original Stu.ca, 26% (20 requests) were made to Fonts.gstatic.com and 8% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Stu.ca.
Page size can be reduced by 748.9 kB (5%)
15.9 MB
15.2 MB
In fact, the total size of Stu.ca main page is 15.9 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 15.5 MB which makes up the majority of the site volume.
Potential reduce by 25.1 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 6.9 kB, which is 21% 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 25.1 kB or 76% of the original size.
Potential reduce by 650.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. St U images are well optimized though.
Potential reduce by 66.3 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 66.3 kB or 19% of the original size.
Potential reduce by 6.7 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. Stu.ca has all CSS files already compressed.
Number of requests can be reduced by 33 (61%)
54
21
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of St U. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
stu.ca
66 ms
www.stu.ca
144 ms
all.css
35 ms
php-blade-calendar.css
30 ms
style-local.css
103 ms
font-awesome.min.css
32 ms
st-updates.css
96 ms
slick.css
96 ms
slick-theme.css
95 ms
css2
41 ms
style2020.css
93 ms
js
57 ms
psrr15470.css
135 ms
modernizr.js
146 ms
jquery.min.js
251 ms
foundation.min.js
259 ms
foundation-datepicker.js
268 ms
combined-js-files.js
258 ms
match-height.js
268 ms
responsive-tables.js
343 ms
php-events-calendar.js
344 ms
slick.js
343 ms
t4-custom.min.js
343 ms
gtm.js
158 ms
OeugyEPHdBs
305 ms
STU_FullColour_Digital.png
337 ms
Spring-Banner-2024.jpg
1301 ms
hp_applynow.jpg
1035 ms
FB-MFC.jpg
586 ms
Spring-Convocation-Feature-Box.jpg
1042 ms
First-year-course-registration-opens-.jpg
800 ms
MMH-3.jpg
1264 ms
athletes_HP.jpg
1153 ms
virtual_events-fs_featurebox.jpg
939 ms
line-2427x32.jpg
1035 ms
STU_FooterLogo_New2023.png
1155 ms
analytics.js
184 ms
pxiGyp8kv8JHgFVrJJLedw.ttf
183 ms
pxiDyp8kv8JHgFVrJJLmg1hlEA.ttf
232 ms
pxiDyp8kv8JHgFVrJJLm21llEA.ttf
385 ms
pxiDyp8kv8JHgFVrJJLmv1plEA.ttf
385 ms
pxiAyp8kv8JHgFVrJJLmE3tF.ttf
386 ms
pxiDyp8kv8JHgFVrJJLmr19lEA.ttf
396 ms
pxiDyp8kv8JHgFVrJJLmy15lEA.ttf
394 ms
pxiDyp8kv8JHgFVrJJLm111lEA.ttf
395 ms
pxiDyp8kv8JHgFVrJJLm81xlEA.ttf
463 ms
pxiEyp8kv8JHgFVrFJA.ttf
460 ms
pxiByp8kv8JHgFVrLGT9V1s.ttf
460 ms
pxiByp8kv8JHgFVrLDz8V1s.ttf
463 ms
pxiByp8kv8JHgFVrLFj_V1s.ttf
462 ms
pxiGyp8kv8JHgFVrLPTedw.ttf
462 ms
pxiByp8kv8JHgFVrLEj6V1s.ttf
498 ms
pxiByp8kv8JHgFVrLCz7V1s.ttf
491 ms
pxiByp8kv8JHgFVrLDD4V1s.ttf
498 ms
pxiByp8kv8JHgFVrLBT5V1s.ttf
498 ms
fontawesome-webfont.woff
65 ms
events.js
384 ms
js
152 ms
fbevents.js
302 ms
emergency.json
887 ms
www-player.css
177 ms
www-embed-player.js
254 ms
base.js
336 ms
collect
147 ms
collect
159 ms
main.MWNkMWZjOGNjMA.js
36 ms
ga-audiences
394 ms
ad_status.js
255 ms
asmjs.js
133 ms
LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js
183 ms
embed.js
54 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
22 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
24 ms
spacer.gif
198 ms
Create
137 ms
id
107 ms
GenerateIT
20 ms
print.css
31 ms
stu.ca accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
stu.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
stu.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 Stu.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 Stu.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.
stu.ca
Open Graph data is detected on the main page of St U. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: