Skip to content
Audit Complete

Results for https://ucalgary.ca

Visit site
CA · CAD (CA$) · Estimated Applicable regulations: PIPEDA · ACA Dev cost: CA$ 95/hr How jurisdiction is detected
Spain Spain · Madrid Completed: Apr 21, 2026 21:21 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C74

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Room to improve — your 15.3s load time is above Google's 2.5s 'Good' threshold.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Drupal · 219 peers
You 74
·
Avg 73
At average
0 50 100
Better than 46% of Drupal sites See full Drupal benchmark →
Adobe Fonts · 141 peers
You 74
·
Avg 73
At average
0 50 100
Better than 54% of Adobe Fonts sites See full Adobe Fonts benchmark →

Top Priorities (5)

1

2 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
2

5 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
3

Soft 404: server returns HTTP 200 for non-existent pages

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › 404 Error Page
4

120 HTTP requests — consider bundling or reducing

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

71 third-party resources (71% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

0

High impact, low effort — start here.

Nothing in this quadrant — good news.

Strategic

5

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fucalgary.ca)](https://beavercheck.com/results/8a732978-ffc5-4931-9579-67f4a917469f)
<a href="https://beavercheck.com/results/8a732978-ffc5-4931-9579-67f4a917469f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fucalgary.ca" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fucalgary.ca

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 15.3s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your audience reach.

3 accessibility issues exclude users who rely on assistive technology.
Your LCP is 15.3s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~29%.

Speed (2)

Page takes 15.3s to load

+12% bounce

Users abandon at ~3s — you're 12.8s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 1.2s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (2)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

10 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

CAD 808 investment → CAD 1.24/month returns + CAD 350,000 risk avoided

Payback period: > 2 years First-year ROI: -98%

Investment

CAD 808

8h · 5 findings

Monthly returns

CAD 1.24 /mo

~CAD 15 / year

  • Bandwidth savings CAD 1.24

Regulatory risk avoided

CAD 350,000

if kept compliant

  • ACA CAD 250,000
  • PIPEDA CAD 100,000

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

CA$808

8.5 developer hours at CA$95/hr

Based on Canada rates (CA$95/hr)

Cost by category

Cost by effort level

Adjust assumptions
CA$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

CAD 29,168 / month at risk

~CAD 350,015 / year if left unfixed

Compliance Risk

CAD 350,000

ACAPIPEDA
  • No privacy policy link detected
    PIPEDA: CAD 1,000 – CAD 100,000
  • 1 advertising/retargeting trackers detected
    PIPEDA: CAD 1,000 – CAD 100,000
  • Trackers detected but no cookie policy found
    PIPEDA: CAD 1,000 – CAD 100,000

+3 more

Bandwidth Waste

CAD 1.24 /mo

11462.1 MB/mo × 0.108 CAD/GB

  • Optimize transfer: save ~1.1 MB per page load
    Saves CAD 1.24/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 3 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

32
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
93
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

8.99 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

15.28 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

1.22 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.018

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

9.68 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

28.45 s

Detailed Report

Audit breakdown by category with detailed findings.

32

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:18.341 source:map[column:197 line:890 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-X4GN9Y4W7D urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:32.054 source:map[column:55 line:887 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-X4GN9Y4W7D urlProvider:network]] map[reflowTime:0.112 source:map[column:23219 line:1 type:source-location url:https://scripts.clarity.ms/0.8.60-beta/clarity.js urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: 60 years of impact – and we’re just getting started
path: 1,HTML,1,BODY,5,MAIN,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,8,IMG
selector: div.row > div.col-image > picture > img
snippet: <img loading="eager" width="1920" height="768" src="https://ucalgary.ca/sites/default/homepage/files/styles/ucws_hero_cta_larg…" alt="60 years of impact – and we’re just getting started">

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
ucalgary.ca/http/1.1
/sites/default/homepage/files/google_tag/ucalgary_homepag...http/1.1
/sites/default/homepage/files/google_tag/ucalgary_main_do...http/1.1
/sites/default/homepage/files/css/css_eOIAjBTp8ohJ2b2Lfe3...http/1.1
/sites/default/homepage/files/css/css_dACxC92wwQ9TJAHC5Kl...http/1.1
/sites/default/homepage/files/css/css_L4aSHvZSyr5SSMJ5qTJ...http/1.1
/sites/default/homepage/files/css/css_DooZ7wtUNWwlbh9SoT2...http/1.1
/sites/default/homepage/files/css/css_iQNMzgu5dzTVSBp-v8-...http/1.1
/sites/default/homepage/files/css/css_uL6IGMipszbWr1xzCjU...http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/UCalgary_Anniversary.svghttp/1.1
/sites/default/homepage/files/styles/ucws_hero_cta_large_...http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/start-something.svghttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/social-icon-facebook-round.svghttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/social-icon-x-round.svghttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/social-icon-linkedin-round.svghttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/social-icon-instagram-round.svghttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/social-icon-youtube-round.svghttp/1.1
/sites/default/homepage/files/js/js_1QFov87KF57H9ld2qVvtH...http/1.1
/sites/default/homepage/files/js/js_3sQAg8RflNvoXl75LSs3m...http/1.1
/sites/default/homepage/files/css/css_tbumLIpsbevq-1JE8sM...http/1.1
/sites/default/homepage/files/css/css_eb1koL5D6KLZ2a-Vh8F...http/1.1
/sites/default/homepage/files/css/css_d4mPdBp3qxOmGWl-WZI...http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/site.webmanifesthttp/1.1
/sites/default/homepage/files/styles/ucws_image_with_text...http/1.1
ucalgary.ca/sites/default/files/micon/ucws-info-shim/fonts/ucws-info-shim.woff2http/1.1
ucalgary.ca/sites/default/files/micon/ucws-more-info/fonts/ucws-more-info.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/icons/fonts/ucalgary.ttf?j3vfz6=http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-regular-webfont.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-semibold-webfont.woff2http/1.1
/sites/default/files/micon/ucws-design-and-digital/fonts/...http/1.1
ucalgary.ca/sites/default/files/micon/ucws-people/fonts/ucws-people.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-medium-webfont.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-bold-webfont.woff2http/1.1
/sites/default/homepage/files/styles/ucws_image_with_text...http/1.1
/sites/default/homepage/files/styles/ucws_image_mobile/pu...http/1.1
/sites/default/homepage/files/styles/ucws_image_mobile/pu...http/1.1
/sites/default/homepage/files/styles/ucws_image_mobile/pu...http/1.1
ucalgary.ca/core/modules/statistics/statistics.phphttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/cookie-dude.gifhttp/1.1
/modules/ucalgary/ucws_blocks/ucws_progress/templates/ani...http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-boldit-webfont.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-regularit-webfont.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/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
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.

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
A group of people dressed as dinosaurs div.rounded-box > div.sidekick-image > picture > img.img-fluid
/sites/default/homepage/files/styles/ucws_image_with_text...89.6 KiB56.7 KiB

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

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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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.

Estimated savings: 340 ms 64.3 KiB
URLTransfer SizeEst Savings
/sites/default/homepage/files/css/css_DooZ7wtUNWwlbh9SoT2...67.0 KiB64.3 KiB

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

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 Evaluation3.2 s
Style & Layout737 ms
Other719 ms
Script Parsing & Compilation452 ms
Rendering239 ms
Parse HTML & CSS97 ms
Garbage Collection33 ms

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

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 159 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 190 ms
Server Backend Latencies 210 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 200 ms
Avoid large layout shifts 15 layout shifts found
INP breakdown
Avoid non-composited animations
93

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.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#footer-links > ul.social > li > a.btn-social div#footer-links > ul.social > li > a.btn-social
div#footer-links > ul.social > li > a.btn-social div#footer-links > ul.social > li > a.btn-social
div#footer-links > ul.social > li > a.btn-social div#footer-links > ul.social > li > a.btn-social
div#footer-links > ul.social > li > a.btn-social div#footer-links > ul.social > li > a.btn-social
div#footer-links > ul.social > li > a.btn-social div#footer-links > ul.social > li > a.btn-social

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Website Terms & Conditions div.row > div#footer-links > p.legalese > a
Privacy Policy div.row > div#footer-links > p.legalese > a
Website feedback div.row > div#footer-links > p.legalese > a

These items highlight common accessibility best practices.

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
`[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
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
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
`<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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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.
Elements with visible text labels have matching accessible names.
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
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.
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
The Content-Security-Policy directive 'frame-ancestors' contains 'default-src' as a source expression. Did you want to add it as a directive and forget a semicolon?
The Content-Security-Policy directive 'frame-ancestors' contains 'default-src' as a source expression. Did you want to add it as a directive and forget a semicolon?
The Content-Security-Policy directive 'frame-ancestors' contains 'default-src' as a source expression. Did you want to add it as a directive and forget a semicolon?
The Content-Security-Policy directive 'frame-ancestors' contains 'default-src' as a source expression. Did you want to add it as a directive and forget a semicolon?
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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

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.

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

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 are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

37
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
97
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.77 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.45 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

39 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

1.007

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.97 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

6.91 s

Detailed Report

Audit breakdown by category with detailed findings.

37

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:1.006753] map[node:map[boundingRect:map[bottom:940 height:940 left:0 right:1350 top:0 width:1350] lhId:page-2-BODY nodeLabel:body.anniversary path:1,HTML,1,BODY selector:body.anniversary snippet:<body class="anniversary eu-cookie-compliance-popup-open eu-cookie-compliance-status-nu…" data-eu-cookie-compliance-once="true"> type:node] score:1 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:733 height:600 left:-75 right:1425 top:133 width:1500] lhId:page-0-IMG nodeLabel:60 years of impact – and we’re just getting started path:1,HTML,1,BODY,5,MAIN,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,8,IMG selector:div.row > div.col-image > picture > img snippet:<img loading="eager" width="1920" height="768" src="https://ucalgary.ca/sites/default/homepage/files/styles/ucws_hero_cta_larg…" alt="60 years of impact – and we’re just getting started"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:604 height:342 left:105 right:655 top:262 width:550] lhId:page-4-DIV nodeLabel:60 years of impact – and we’re just getting started What began as a bold visio… path:1,HTML,1,BODY,5,MAIN,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV selector:div.row > div.col-text > div.cta-wrapper > div.cta-content snippet:<div class="cta-content dark no-shadow left"> type:node] score:0.003018 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:4899 height:36 left:515 right:835 top:4862 width:320] lhId:page-18-IMG nodeLabel:Start Something path:1,HTML,1,BODY,6,FOOTER,1,DIV,1,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div.row > div#footer-special > a > img snippet:<img src="/themes/ucalgary/ucws_theme/images/start-something.svg" width="320" height="35" alt="Start Something"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:827 height:44 left:105 right:1245 top:783 width:1140] lhId:page-10-H2 nodeLabel:Start Something. path:1,HTML,1,BODY,5,MAIN,3,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,H2 selector:div.container > div.row > div.col-12 > h2 snippet:<h2> type:node] score:0.000374 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:4899 height:36 left:515 right:835 top:4862 width:320] lhId:page-18-IMG nodeLabel:Start Something path:1,HTML,1,BODY,6,FOOTER,1,DIV,1,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div.row > div#footer-special > a > img snippet:<img src="/themes/ucalgary/ucws_theme/images/start-something.svg" width="320" height="35" alt="Start Something"> type:node]] map[cause:Web font extra:map[type:url value:https://ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-semibold-webfont.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:940 height:112 left:0 right:1350 top:828 width:1350] lhId:page-17-DIV nodeLabel:This site uses cookies. By continuing, you're agreeing to the use of cookies ou… path:1,HTML,1,BODY,0,DIV selector:body.anniversary > div#sliding-popup snippet:<div id="sliding-popup" role="alertdialog" aria-describedby="popup-text" aria-label="Cookie compliance banner" style="height: auto; width: 100%; bottom: 0px;" class="sliding-popup-bottom"> type:node] score:0.00032 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1995 height:240 left:885 right:1245 top:1755 width:360] lhId:page-20-IMG nodeLabel:Space path:1,HTML,1,BODY,5,MAIN,4,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,A,0,PICTURE,6,IMG selector:div > a > picture > img.img-fluid snippet:<img class="img-fluid" loading="lazy" width="1140" height="761" src="https://ucalgary.ca/sites/default/homepage/files/styles/ucws_image_desktop…" alt="Space"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:940 height:112 left:0 right:1350 top:828 width:1350] lhId:page-17-DIV nodeLabel:This site uses cookies. By continuing, you're agreeing to the use of cookies ou… path:1,HTML,1,BODY,0,DIV selector:body.anniversary > div#sliding-popup snippet:<div id="sliding-popup" role="alertdialog" aria-describedby="popup-text" aria-label="Cookie compliance banner" style="height: auto; width: 100%; bottom: 0px;" class="sliding-popup-bottom"> type:node] score:0.00029 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1995 height:240 left:885 right:1245 top:1755 width:360] lhId:page-20-IMG nodeLabel:Space path:1,HTML,1,BODY,5,MAIN,4,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,A,0,PICTURE,6,IMG selector:div > a > picture > img.img-fluid snippet:<img class="img-fluid" loading="lazy" width="1140" height="761" src="https://ucalgary.ca/sites/default/homepage/files/styles/ucws_image_desktop…" alt="Space"> type:node]]] type:subitems]]]

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:39.45 source:map[column:197 line:885 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-X4GN9Y4W7D urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:52.88 source:map[column:376 line:836 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-X4GN9Y4W7D urlProvider:network]] map[reflowTime:14.96 source:map[column:23219 line:1 type:source-location url:https://scripts.clarity.ms/0.8.60-beta/clarity.js urlProvider:network]] map[reflowTime:49.029 source:map[type:text value:[unattributed]]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: 60 years of impact – and we’re just getting started
path: 1,HTML,1,BODY,5,MAIN,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,8,IMG
selector: div.row > div.col-image > picture > img
snippet: <img loading="eager" width="1920" height="768" src="https://ucalgary.ca/sites/default/homepage/files/styles/ucws_hero_cta_larg…" alt="60 years of impact – and we’re just getting started">

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
ucalgary.ca/http/1.1
/sites/default/homepage/files/google_tag/ucalgary_homepag...http/1.1
/sites/default/homepage/files/google_tag/ucalgary_main_do...http/1.1
/sites/default/homepage/files/css/css_eOIAjBTp8ohJ2b2Lfe3...http/1.1
/sites/default/homepage/files/css/css_dACxC92wwQ9TJAHC5Kl...http/1.1
/sites/default/homepage/files/css/css_L4aSHvZSyr5SSMJ5qTJ...http/1.1
/sites/default/homepage/files/css/css_DooZ7wtUNWwlbh9SoT2...http/1.1
/sites/default/homepage/files/css/css_iQNMzgu5dzTVSBp-v8-...http/1.1
/sites/default/homepage/files/css/css_uL6IGMipszbWr1xzCjU...http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/UCalgary_Anniversary.svghttp/1.1
/sites/default/homepage/files/styles/ucws_hero_cta_large_...http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/start-something.svghttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/social-icon-facebook-round.svghttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/social-icon-x-round.svghttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/social-icon-linkedin-round.svghttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/social-icon-instagram-round.svghttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/social-icon-youtube-round.svghttp/1.1
/sites/default/homepage/files/js/js_1QFov87KF57H9ld2qVvtH...http/1.1
/sites/default/homepage/files/js/js_3sQAg8RflNvoXl75LSs3m...http/1.1
/sites/default/homepage/files/css/css_tbumLIpsbevq-1JE8sM...http/1.1
/sites/default/homepage/files/css/css_eb1koL5D6KLZ2a-Vh8F...http/1.1
/sites/default/homepage/files/css/css_d4mPdBp3qxOmGWl-WZI...http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/site.webmanifesthttp/1.1
/sites/default/homepage/files/styles/ucws_image_with_text...http/1.1
ucalgary.ca/sites/default/files/micon/ucws-info-shim/fonts/ucws-info-shim.woff2http/1.1
ucalgary.ca/sites/default/files/micon/ucws-more-info/fonts/ucws-more-info.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/icons/fonts/ucalgary.ttf?j3vfz6=http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-regular-webfont.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-semibold-webfont.woff2http/1.1
/sites/default/files/micon/ucws-design-and-digital/fonts/...http/1.1
ucalgary.ca/sites/default/files/micon/ucws-people/fonts/ucws-people.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-medium-webfont.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-bold-webfont.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-regularit-webfont.woff2http/1.1
/sites/default/homepage/files/styles/ucws_image_desktop/p...http/1.1
/sites/default/homepage/files/styles/ucws_image_desktop/p...http/1.1
/sites/default/homepage/files/styles/ucws_image_desktop/p...http/1.1
/sites/default/homepage/files/styles/ucws_banner_large_de...http/1.1
ucalgary.ca/core/modules/statistics/statistics.phphttp/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/images/cookie-dude.gifhttp/1.1
/modules/ucalgary/ucws_blocks/ucws_progress/templates/ani...http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/fonts/proximanova-boldit-webfont.woff2http/1.1
ucalgary.ca/themes/ucalgary/ucws_theme/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
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.

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
A group of people in the lab div > a > picture > img.img-fluid
/sites/default/homepage/files/styles/ucws_image_desktop/p...66.9 KiB57.6 KiB
A group of people together div > a > picture > img.img-fluid
/sites/default/homepage/files/styles/ucws_image_desktop/p...63.7 KiB57.3 KiB
A group of people dressed as dinosaurs div.row > div.col-12 > div.rounded-box > div.sidekick-image
/sites/default/homepage/files/styles/ucws_image_with_text...86.9 KiB49.8 KiB
Calgary Peace Bridge div.row > div.col-image > picture > img
/sites/default/homepage/files/styles/ucws_banner_large_de...116.1 KiB45.2 KiB
Space div > a > picture > img.img-fluid
/sites/default/homepage/files/styles/ucws_image_desktop/p...34.7 KiB31.2 KiB
60 years of impact – and we’re just getting started div.row > div.col-image > picture > img
/sites/default/homepage/files/styles/ucws_hero_cta_large_...61.0 KiB23.8 KiB

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
body.anniversary body.anniversary
1.000
60 years of impact – and we’re just getting started What began as a bold visio… div.row > div.col-text > div.cta-wrapper > div.cta-content
0.003
Start Something. div.container > div.row > div.col-12 > h2
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000
What began as a bold vision has grown over six decades into a place that helps … div.col-text > div.cta-wrapper > div.cta-content > p
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000
This site uses cookies. By continuing, you're agreeing to the use of cookies ou… body.anniversary > div#sliding-popup
0.000

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

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.

Estimated savings: 60 ms 62.4 KiB
URLTransfer SizeEst Savings
/sites/default/homepage/files/css/css_DooZ7wtUNWwlbh9SoT2...67.0 KiB62.4 KiB

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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

Document request latency
Optimize DOM size
LCP breakdown
Optimize viewport for mobile
Max Potential First Input Delay 70 ms
Minify CSS
Minify JavaScript
User Timing marks and measures 15 user timings
JavaScript execution time 0.7 s
Minimizes main-thread work 1.6 s
Avoid long main-thread tasks 4 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 190 ms
Server Backend Latencies 320 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 210 ms
INP breakdown
Avoid non-composited animations
97

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.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#footer-links > ul.social > li > a.btn-social div#footer-links > ul.social > li > a.btn-social
div#footer-links > ul.social > li > a.btn-social div#footer-links > ul.social > li > a.btn-social
div#footer-links > ul.social > li > a.btn-social div#footer-links > ul.social > li > a.btn-social
div#footer-links > ul.social > li > a.btn-social div#footer-links > ul.social > li > a.btn-social
div#footer-links > ul.social > li > a.btn-social div#footer-links > ul.social > li > a.btn-social

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.

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
`[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
Form elements have associated labels
`[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
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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
Identical links have the same purpose.
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
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
`<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
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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.
Elements with visible text labels have matching accessible names.
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
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.
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
The Content-Security-Policy directive 'frame-ancestors' contains 'default-src' as a source expression. Did you want to add it as a directive and forget a semicolon?
The Content-Security-Policy directive 'frame-ancestors' contains 'default-src' as a source expression. Did you want to add it as a directive and forget a semicolon?
The Content-Security-Policy directive 'frame-ancestors' contains 'default-src' as a source expression. Did you want to add it as a directive and forget a semicolon?
The Content-Security-Policy directive 'frame-ancestors' contains 'default-src' as a source expression. Did you want to add it as a directive and forget a semicolon?
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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

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.

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

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 are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback