Moe.gov.sa وزارة التعليم
الموقع الرسمي لوزارة التعليم , تعليم متميز لبناء مجتمع معرفي منافس عالمياً. توفير فرصة التعليم للجميع في بيئة تعليمية مناسبة
moe.gov.sa Desktop Performance
40/100
These metrics represent real-world Chrome users experience viewing moe.gov.sa web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
Cumulative Layout Shift
First Input Delay
First Contentful Paint
Largest Contentful Paint
Metrics
Speed Index0/100 7.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First Contentful Paint6/100 3.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Largest Contentful Paint20/100 3.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Time to Interactive52/100 4.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time86/100 170 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift98/100 0.053
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (21)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 3,390 ms
3,385 ms
Reduce initial server response time
Root document took 2,890 ms
2,292 ms
Serve images in next-gen formats
Potential savings of 967 KiB
680 ms
Remove unused CSS
Potential savings of 105 KiB
400 ms
Avoid multiple page redirects
Potential savings of 340 ms
340 ms
Remove unused JavaScript
Potential savings of 292 KiB
200 ms
Minify CSS
Potential savings of 17 KiB
120 ms
Minify JavaScript
Potential savings of 57 KiB
80 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
Ensure text remains visible during webfont load
Avoid `document.write()`
Reduce the impact of third-party code
Third-party code blocked the main thread for 430 ms
Avoid an excessive DOM size
1,751 elements
Serve static assets with an efficient cache policy
35 resources found
Minimize main-thread work
2.3 s
Avoid enormous network payloads
Total size was 2,783 KiB
Avoid long main-thread tasks
5 long tasks found
Largest Contentful Paint element
1 element found
Avoid chaining critical requests
54 chains found
Keep request counts low and transfer sizes small
157 requests • 2,783 KiB
Avoid large layout shifts
5 elements found
Passed Audits (8)
Preload key requests
Defer offscreen images
Preconnect to required origins
Use video formats for animated content
JavaScript execution time
0.9 s
Efficiently encode images
Properly size images
Potential savings of 17 KiB
Enable text compression
Potential savings of 2 KiB
moe.gov.sa Desktop SEO
92/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (1)
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Passed Audits (11)
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Page isn’t blocked from indexing
Document has a `<title>` element
Image elements have `[alt]` attributes
Document avoids plugins
robots.txt is valid
Document has a valid `rel=canonical`
Document has a meta description
Page has successful HTTP status code
Document has a valid `hreflang`
Links have descriptive text
moe.gov.sa Desktop Best Practices
62/100
These checks highlight opportunities to improve the overall code health of moe.gov.sa page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (5)
General
Browser errors were logged to the console
Trust and Safety
Links to cross-origin destinations are unsafe
Does not use HTTPS
1 insecure request found
Includes front-end JavaScript libraries with known security vulnerabilities
9 vulnerabilities detected
User Experience
Displays images with incorrect aspect ratio
Passed Audits (9)
Avoids deprecated APIs
Avoids requesting the notification permission on page load
Allows users to paste into password fields
Avoids Application Cache
Avoids requesting the geolocation permission on page load
Detected JavaScript libraries
Page has the HTML doctype
Serves images with appropriate resolution
Properly defines charset
moe.gov.sa Desktop Progressive Web App
19/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (10)
PWA Optimized
Does not provide a valid `apple-touch-icon`
Is not configured for a custom splash screen
Does not set a theme color for the address bar.
Manifest doesn't have a maskable icon
Fast and reliable
Current page does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 23.9 s
`start_url` does not respond with a 200 when offline
Installable
Does not use HTTPS
1 insecure request found
Does not register a service worker that controls page and `start_url`
Web app manifest does not meet the installability requirements
Passed Audits (3)
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Redirects HTTP traffic to HTTPS
Contains some content when JavaScript is not available
moe.gov.sa Desktop Accessibility
85/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (5)
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.
Form elements do not have associated labels
Links do not have a discernible name
`<frame>` or `<iframe>` elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (18)
`[role]`s are contained by their required parent element
Document has a `<title>` element
Image elements have `[alt]` attributes
ARIA IDs are unique
`[role]`s have all required `[aria-*]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Buttons have an accessible name
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[id]` attributes on active, focusable elements are unique
`<html>` element has a `[lang]` attribute
`[aria-hidden="true"]` is not present on the document `<body>`
`<html>` element has a valid value for its `[lang]` attribute
`[role]` values are valid
No element has a `[tabindex]` value greater than 0
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
The page contains a heading, skip link, or landmark region
Desktop Speed
63/100
These checks analyze the performance of moe.gov.sa on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (7)
Optimize images
Leverage browser caching
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Prioritize visible content
Minify JavaScript
Minify CSS
Reduce server response time
Passed Audits (3)
Avoid landing page redirects
Enable compression
Minify HTML
www.moe.com
www.moe.net
www.moe.org
www.moe.info
www.moe.biz
www.moe.us
www.moe.mobi
www.oe.gov.sa
www.moe.gov.sa
www.noe.gov.sa
www.mnoe.gov.sa
www.nmoe.gov.sa
www.joe.gov.sa
www.mjoe.gov.sa
www.jmoe.gov.sa
www.koe.gov.sa
www.mkoe.gov.sa
www.kmoe.gov.sa
www.me.gov.sa
www.mie.gov.sa
www.moie.gov.sa
www.mioe.gov.sa
www.mke.gov.sa
www.moke.gov.sa
www.mle.gov.sa
www.mole.gov.sa
www.mloe.gov.sa
www.mpe.gov.sa
www.mope.gov.sa
www.mpoe.gov.sa
www.mo.gov.sa
www.mow.gov.sa
www.moew.gov.sa
www.mowe.gov.sa
www.mos.gov.sa
www.moes.gov.sa
www.mose.gov.sa
www.mod.gov.sa
www.moed.gov.sa
www.mode.gov.sa
www.mor.gov.sa
www.moer.gov.sa
www.more.gov.sa
www.moe.net
www.moe.org
www.moe.info
www.moe.biz
www.moe.us
www.moe.mobi
www.oe.gov.sa
www.moe.gov.sa
www.noe.gov.sa
www.mnoe.gov.sa
www.nmoe.gov.sa
www.joe.gov.sa
www.mjoe.gov.sa
www.jmoe.gov.sa
www.koe.gov.sa
www.mkoe.gov.sa
www.kmoe.gov.sa
www.me.gov.sa
www.mie.gov.sa
www.moie.gov.sa
www.mioe.gov.sa
www.mke.gov.sa
www.moke.gov.sa
www.mle.gov.sa
www.mole.gov.sa
www.mloe.gov.sa
www.mpe.gov.sa
www.mope.gov.sa
www.mpoe.gov.sa
www.mo.gov.sa
www.mow.gov.sa
www.moew.gov.sa
www.mowe.gov.sa
www.mos.gov.sa
www.moes.gov.sa
www.mose.gov.sa
www.mod.gov.sa
www.moed.gov.sa
www.mode.gov.sa
www.mor.gov.sa
www.moer.gov.sa
www.more.gov.sa