Skip to content
https://yorku.ca

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

51

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:60.114 source:map[type:text value:[unattributed]]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-359319 div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-359319
www.yorku.ca/wp-content/uploads/2026/03/25000-HP-APR-2026-1536x1486.jpg581.1 KiB490.8 KiB
Three York University graduate students talking together inside campus building div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-358623
www.yorku.ca/homepage2/wp-content/uploads/sites/1004/2025/08/img_02-1024x685.jpg114.5 KiB84.4 KiB
York University undergraduate student exploring virtual reality technology. div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-358622
www.yorku.ca/homepage2/wp-content/uploads/sites/1004/2025/08/img_01-1024x685.jpg82.4 KiB60.7 KiB
York University div.york2025-header-top > div#site-title > a > img.yu-logo
www.yorku.ca/wp-content/themes/york2020/images/yorku-logo.jpg68.5 KiB52.2 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:2995.649 label:Time to first byte subpart:timeToFirstByte] map[duration:245.605 label:Resource load delay subpart:resourceLoadDelay] map[duration:2560.319 label:Resource load duration subpart:resourceLoadDuration] map[duration:132.275 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-359319
path: 1,HTML,1,BODY,21,DIV,1,DIV,0,MAIN,0,ARTICLE,0,DIV,0,DIV,0,DIV,1,DIV,0,FIGURE,0,IMG
selector: div.wp-block-columns > div.wp-block-column > figure.wp-block-image > img.wp-image-359319
snippet: <img fetchpriority="high" decoding="async" width="1550" height="1500" src="https://www.yorku.ca/wp-content/uploads/2026/03/25000-HP-APR-2026-1536x148…" alt="" class="wp-image-359319" srcset="https://www.yorku.ca/wp-content/uploads/2026/03/25000-HP-APR-2026.jpg 1550…" sizes="(max-width: 1550px) 100vw, 1550px">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.yorku.ca/http/1.1
/wp-content/themes/york2025-homepage/assets/icons/menu-ar...http/1.1
/wp-content/themes/york2025-homepage/assets/icons/menu-ar...http/1.1
/wp-content/themes/york2025-homepage/assets/icons/menu-ar...http/1.1
/wp-content/themes/york2025-homepage/assets/icons/menu-ar...http/1.1
www.yorku.ca/wp-content/themes/york2025-homepage/assets/icons/arrow-left.svghttp/1.1
www.yorku.ca/wp-includes/css/dist/block-library/style.min.css?ver=6.9.4http/1.1
www.yorku.ca/wp-includes/blocks/cover/style.min.css?ver=6.9.4http/1.1
www.yorku.ca/wp-content/themes/york2020/site.webmanifesthttp/1.1
www.yorku.ca/wp-content/plugins/yorkublocks-v1.3/dist/style.css?ver=6.9.4http/1.1
/wp-content/themes/york2025-homepage/assets/js/swiper/swi...http/1.1
www.yorku.ca/wp-content/plugins/yu-blockpatterns/style.css?ver=1769698391http/1.1
www.yorku.ca/wp-content/uploads/font-awesome/v6.4.2/css/svg-with-js.csshttp/1.1
www.yorku.ca/wp-content/themes/york2020/style.css?ver=6.9.4http/1.1
www.yorku.ca/wp-content/themes/york2025-homepage/style.css?ver=1.0.2http/1.1
/wp-content/themes/york2025-homepage/assets/css/style.min...http/1.1
/wp-content/themes/york2025-homepage/assets/fonts/theme-i...http/1.1
www.yorku.ca/wp-includes/css/dashicons.min.css?ver=6.9.4http/1.1
/wp-content/plugins/cred-frontend-editor/vendor/toolset/t...http/1.1
/wp-content/plugins/cred-frontend-editor/vendor/toolset/c...http/1.1
www.yorku.ca/wp-includes/js/jquery/jquery.min.js?ver=3.7.1http/1.1
www.yorku.ca/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1http/1.1
www.yorku.ca/wp-content/uploads/2026/03/25000-HP-APR-2026-1536x1486.jpghttp/1.1
www.yorku.ca/wp-content/plugins/yu-blockpatterns/script.js?ver=1769696935http/1.1
/wp-content/plugins/yorkublocks-v1.3/src/blocks/tabbed-ne...http/1.1
www.yorku.ca/wp-content/plugins/yorkublocks-v1.3/src/scrollby-polyfill.jshttp/1.1
/wp-content/themes/york2025-homepage/assets/js/mobile-men...http/1.1
/wp-content/themes/york2025-homepage/assets/js/theme-scri...http/1.1
www.yorku.ca/wp-content/themes/york2020/js/popper.min.js?ver=6.9.4http/1.1
www.yorku.ca/wp-content/themes/york2020/js/bootstrap.min.js?ver=6.9.4http/1.1
www.yorku.ca/wp-content/themes/york2020/js/dropdown.js?ver=6.9.4http/1.1
www.yorku.ca/wp-content/themes/york2020/js/nav.js?ver=6.9.4http/1.1
www.yorku.ca/wp-includes/js/jquery/ui/core.min.js?ver=1.13.3http/1.1
www.yorku.ca/wp-includes/js/jquery/ui/datepicker.min.js?ver=1.13.3http/1.1
www.yorku.ca/wp-includes/js/underscore.min.js?ver=1.13.7http/1.1
www.yorku.ca/wp-includes/js/jquery/suggest.min.js?ver=1.1-20110113http/1.1
/wp-content/plugins/cred-frontend-editor/vendor/toolset/t...http/1.1
/wp-content/plugins/cred-frontend-editor/vendor/toolset/t...http/1.1
/wp-content/plugins/kadence-blocks/includes/assets/js/cou...http/1.1
/wp-content/plugins/kadence-blocks/includes/assets/js/kb-...http/1.1
/wp-content/plugins/wp-smush-pro/app/assets/js/smush-lazy...http/1.1
/wp-content/themes/york2025-homepage/blocks/testimonials-...http/1.1
/wp-content/themes/york2025-homepage/assets/js/swiper/swi...http/1.1
www.yorku.ca/wp-content/plugins/yorkublocks-v1.3/dist/script.js?ver=6.9.4http/1.1
www.yorku.ca/wp-content/themes/york2025-homepage/assets/icons/quotes.svghttp/1.1
/wp-content/themes/york2025-homepage/assets/fonts/theme-i...http/1.1
www.yorku.ca/wp-content/uploads/2025/08/New-website-video_Final.mp4http/1.1
www.yorku.ca/wp-content/themes/york2020/images/yorku-logo.jpghttp/1.1
www.yorku.ca/wp-content/uploads/2026/04/life-long-bg-1024x547.pnghttp/1.1
www.yorku.ca/wp-content/uploads/2026/04/double-arrow-right.pnghttp/1.1
www.yorku.ca/homepage2/wp-content/uploads/sites/1004/2025/08/img_01-1024x685.jpghttp/1.1
www.yorku.ca/homepage2/wp-content/uploads/sites/1004/2025/08/img_02-1024x685.jpghttp/1.1
www.yorku.ca/wp-includes/js/wp-emoji-release.min.js?ver=6.9.4http/1.1
www.yorku.ca/wp-content/themes/york2020/favicon.icohttp/1.1

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
www.yorku.ca/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.15.3 KiB275 ms
www.yorku.ca/wp-includes/css/dashicons.min.css?ver=6.9.435.4 KiB540 ms
www.yorku.ca/wp-includes/js/jquery/jquery.min.js?ver=3.7.130.2 KiB540 ms
/wp-content/plugins/cred-frontend-editor/vendor/toolset/c...2.3 KiB275 ms
www.yorku.ca/wp-content/themes/york2020/style.css?ver=6.9.429.8 KiB540 ms
/wp-content/plugins/cred-frontend-editor/vendor/toolset/t...2.8 KiB275 ms
/wp-content/themes/york2025-homepage/assets/fonts/theme-i...838 B275 ms
/wp-content/themes/york2025-homepage/assets/css/style.min...4.1 KiB275 ms
www.yorku.ca/wp-content/themes/york2025-homepage/style.css?ver=1.0.2732 B275 ms
www.yorku.ca/wp-content/uploads/font-awesome/v6.4.2/css/svg-with-js.css3.0 KiB806 ms
www.yorku.ca/wp-content/plugins/yu-blockpatterns/style.css?ver=17696983916.1 KiB806 ms
/wp-content/themes/york2025-homepage/assets/js/swiper/swi...5.9 KiB806 ms
www.yorku.ca/wp-content/plugins/yorkublocks-v1.3/dist/style.css?ver=6.9.41.7 KiB806 ms
www.yorku.ca/wp-includes/blocks/cover/style.min.css?ver=6.9.42.2 KiB806 ms
www.yorku.ca/wp-includes/css/dist/block-library/style.min.css?ver=6.9.416.1 KiB275 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.2/css/all.min.css?ver=6.4.219.0 KiB322 ms
use.fontawesome.com/releases/v6.4.2/css/all.css24.3 KiB383 ms
use.fontawesome.com/releases/v6.4.2/css/v4-shims.css4.7 KiB
/css2?family=IBM+Plex+Sans:ital,wght@0,100..700;1,100..70...1.9 KiB
fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@400;500;600&display=swap834 B207 ms

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 936 ms
URLTime Spent
yorku.ca/936 ms
www.yorku.ca/0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.0 s
URLTime Spent
www.yorku.ca/1.1 s

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 270 ms 5.8 KiB
URLTransfer SizeEst Savings
www.yorku.ca/wp-content/themes/york2020/style.css?ver=6.9.429.8 KiB5.8 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.2 s
Other1.0 s
Script Parsing & Compilation245 ms
Style & Layout197 ms
Rendering79 ms
Parse HTML & CSS65 ms
Garbage Collection39 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with WebSocket cannot enter back/forward cache.Pending browser support

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
York University div.york2025-header-top > div#site-title > a > img.yu-logo
www.yorku.ca/wp-content/themes/york2020/images/yorku-logo.jpg

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Max Potential First Input Delay 120 ms
●Layout shift culprits
●Optimize DOM size
●LCP request discovery
●Optimize viewport for mobile
●User Timing marks and measures 13 user timings
●JavaScript execution time 0.9 s
●Avoid long main-thread tasks 10 long tasks found
●Network Requests
●Network Round Trip Times 250 ms
●Server Backend Latencies 270 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○Avoid non-composited animations
89

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Programs nav#navbar > div.container > ul#menu-navigation-1 > li.menu-item
Admissions nav#navbar > div.container > ul#menu-navigation-1 > li.menu-item
Student Life nav#navbar > div.container > ul#menu-navigation-1 > li.menu-item
Research & Innovation nav#navbar > div.container > ul#menu-navigation-1 > li.menu-item
Partnerships & Community nav#navbar > div.container > ul#menu-navigation-1 > li.menu-item
About York nav#navbar > div.container > ul#menu-navigation-1 > li.menu-item

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
View All News div.wp-block-group > div.wp-block-group > p.view-all-wrapper > a

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Programs Admissions Student Life Research & Innovation Partnerships & Community… div.sticky-top > nav#navbar > div.container > ul#menu-navigation-1

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback