Your Website Score is
SEO Rank : 56 Website URL: moodle.loyola.ca Last Updated: 3 months
Success
62% of passed verification steps
Warning
23% of total warning
Errors
15% of total errors, require fast action
Share
Estimation Traffic and Earnings
111
Unique Visits
Daily
205
Pages Views
Daily
$0
Income
Daily
3,108
Unique Visits
Monthly
5,843
Pages Views
Monthly
$0
Income
Monthly
35,964
Unique Visits
Yearly
68,880
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 30%
Domain Authority
Domain Authority 30%
Moz Rank
3.0/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
33 Characters
LOYOLA HIGH SCHOOL ONLINE COURSES
Meta Description
221 Characters
Welcome to the online courses available at Loyola High School.
If you are a student at the school, you should have a username and
password that will bring you to the courses that you are enrolled in.
Enjoy the site.
Effective URL
24 Characters
https://moodle.loyola.ca
Excerpt
Page content
Loyola High School Online Courses
Skip to main content
Side panel
lhs
...
Meta Keywords
2 Detected
Google Preview
Your look like this in google search result
LOYOLA HIGH SCHOOL ONLINE COURSES
https://moodle.loyola.ca
Welcome to the online courses available at Loyola High School.
If you are a student at the school, you should have a username and
password that wi
Robots.txt
File No Found
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~48.19 KB
Code Size: ~39.29 KB
Text Size: ~8.9 KB Ratio: 18.47%
Social Data
Delicious
Total: 0
Facebook
Total: 0
Google
Total: 0
Linkedin
Total: 0
Pinterest
Total: 0
Stumbleupon
Total: 0
Tumblr
Total: 0
Vk
Total: 0
Technologies
PWA - Manifest
Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest
Desktop
Avoid long main-thread tasks
1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimizes main-thread work
0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused CSS
Potential savings of 133 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
First CPU Idle
0.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Avoid serving legacy JavaScript to modern browsers
Potential savings of 1 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Initial server response time was short
Root document took 570 ms
Keep the server response time for the main document short because all other requests depend on it
JavaScript execution time
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Enable text compression
Potential savings of 83 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Time to Interactive
0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint
0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Preload key requests
Potential savings of 440 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.
Minimize third-party usage
Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Keep request counts low and transfer sizes small
25 requests • 1,084 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Estimated Input Latency
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy
10 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids enormous network payloads
Total size was 1,084 KiB
Large network payloads cost users real money and are highly correlated with long load times
Remove unused JavaScript
Potential savings of 540 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid chaining critical requests
7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Largest Contentful Paint
0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Speed Index
1.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First Meaningful Paint
0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Max Potential First Input Delay
50 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Eliminate render-blocking resources
Potential savings of 180 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoids an excessive DOM size
255 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Mobile
Enable text compression
Potential savings of 83 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Document uses legible font sizes
93.71% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Tap targets are not sized appropriately
30% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Page load is not fast enough on mobile networks
Interactive at 10.2 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency
330 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Keep request counts low and transfer sizes small
27 requests • 1,088 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Remove unused JavaScript
Potential savings of 539 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Avoids an excessive DOM size
257 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
First Contentful Paint (3G)
6578 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Minimize main-thread work
7.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Avoid chaining critical requests
7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Reduce JavaScript execution time
3.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive
10.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimize third-party usage
Third-party code blocked the main thread for 110 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Avoids enormous network payloads
Total size was 1,088 KiB
Large network payloads cost users real money and are highly correlated with long load times
First CPU Idle
9.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.
Preload key requests
Potential savings of 2,370 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Initial server response time was short
Root document took 500 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources
Potential savings of 960 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused CSS
Potential savings of 134 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
First Contentful Paint
3.4 s
First Contentful Paint marks the time at which the first text or image is painted
Total Blocking Time
2,270 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy
10 resources found
A long cache lifetime can speed up repeat visits to your page
First Meaningful Paint
3.4 s
First Meaningful Paint measures when the primary content of a page is visible
Max Potential First Input Delay
720 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid serving legacy JavaScript to modern browsers
Potential savings of 1 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Largest Contentful Paint
3.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Speed Index
6.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Speed And Optimization Tips
Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Congratulations! Your site not have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links
View links
| First 20 Links | Relationship | HTTP Status |
| lhs | Internal Link | 200 |
| Student Handbook | Internal Link | 302 |
| Library Page | Internal Link | 302 |
| Library Guide to MLA | Internal Link | 302 |
| English - Pirate (en_ar) | Internal Link | 200 |
| English (en) | Internal Link | 200 |
| English for Workplace (en_wp) | Internal Link | 200 |
| English US - K12 (en_us_k12) | Internal Link | 200 |
| Français - Canada (fr_ca) | Internal Link | 200 |
| Français (fr) | Internal Link | 200 |
| Français pour Workplace (fr_wp) | Internal Link | 200 |
| 简体中文 (zh_cn) | Internal Link | 200 |
| Log in | Internal Link | 200 |
| Home | Internal Link | 200 |
| Calendar | Internal Link | 303 |
| Site news Forum | Internal Link | 200 |
| Forums | Internal Link | 200 |
| This month | Internal Link | 303 |
| 4 | Internal Link | 303 |
| Data retention summary | Internal Link | 200 |
Alexa Rank
0
Local Rank: / Users: / PageViews:2,907,582
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| moodle.loyola.co | Already Registered |
| moodle.loyola.us | Already Registered |
| moodle.loyola.com | Already Registered |
| moodle.loyola.org | Already Registered |
| moodle.loyola.net | Already Registered |
| modle.loyola.ca | Already Registered |
| joodle.loyola.ca | Already Registered |
| ioodle.loyola.ca | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Thu, 05 Nov 2020 00:12:41 GMT
Server: Apache
X-Powered-By: PHP/7.3.6
Content-Language: en
Content-Script-Type: text/javascript
Content-Style-Type: text/css
X-UA-Compatible: IE=edge
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0, no-transform
Pragma: no-cache
Expires: Mon, 20 Aug 1969 09:23:00 GMT
Accept-Ranges: none
Set-Cookie: MoodleSession=466lgdub62iotfeb13jotl95ep; path=/
Last-Modified: Thu, 05 Nov 2020 00:12:41 GMT
Content-Type: text/html; charset=utf-8
Click to Add/Show Comments