Brazil · Sao Paulo Completed: Apr 22, 2026 20:58 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 70 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Good foundation, but a few gaps could be exploited.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Good server performance with room for optimization.
Several regulatory requirements are not yet met.
Missing metadata means poor previews on social media and search.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 5.9 MB (4.0 MB transferred)
Performance issues directly impact user engagement and conversion rates.
59 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/fe994a77-9c5e-4674-bcec-fb3bb147ffcd)<a href="https://beavercheck.com/results/fe994a77-9c5e-4674-bcec-fb3bb147ffcd"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbris.ac.uk" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fbris.ac.ukThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 24.7s 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 user trust.
9 barrier(s) likely increasing bounce by ~38%.
Page takes 24.7s to load
+12% bounceUsers abandon at ~3s — you're 22.2s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 1.8s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No viewport meta tag
+15% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo 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, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
£413 investment → £0.80/month returns + GBP 18,050,000 risk avoided
£413
6h · 5 findings
£0.80 /mo
~£9.58 / year
GBP 18,050,000
if kept compliant
£113 — in quick wins — start here for the fastest payback
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.
5.5 developer hours at £75/hr
Based on United Kingdom rates (£75/hr)
Start here for the best return on investment
£1,504,167 / month at risk
~£18,050,010 / year if left unfixed
£18,050,000
+4 more
£0.80 /mo
12671.4 MB/mo × 0.063 GBP/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
7.42 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
24.75 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.78 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.023
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
9.98 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.
24.75 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
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.
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.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Stone buildings, blue sky, green grass, gazebos and people body > main#main > section#homepage-hero > div.hero__image | www.bristol.ac.uk/media-library/sites/homepage/images/homepage-1.jpg | 516.0 KiB | 310.2 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce?autoBlock=on | 143.6 KiB | 2.3 s |
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.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| bris.ac.uk/ | 1.3 s |
| www.bristol.ac.uk/ | 0.0 ms |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /assets/responsive-web-project/2.7.0/css/responsive-web-p... | 146.2 KiB | 129.9 KiB |
| /assets/responsive-web-project/2.7.0/css/responsive-web-p... | 39.6 KiB | 37.4 KiB |
| /*! normalize.css v8.0.1 | MIT License | github.com/necol... | 40.5 KiB | 32.2 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| /api/v1/gw/static/js/main.www_bristol_ac_uk.hHsrG.v176849... | 295.1 KiB | 141.7 KiB |
| www.bristol.ac.uk/assets/homepage-search/1.0.4/js/chunk-480a6038.24fe62bd.js | 136.2 KiB | 94.4 KiB |
| app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce | 143.2 KiB | 82.5 KiB |
| /assets/responsive-web-project/2.7.0/js/responsive-web-pr... | 75.5 KiB | 71.0 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-MWCJ929 | 194.4 KiB | 57.4 KiB |
| app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce?autoBlock=on | 143.3 KiB | 53.0 KiB |
| www.bristol.ac.uk/assets/homepage-search/1.0.4/js/chunk-vendors.a3cb5fa7.js | 123.5 KiB | 46.3 KiB |
| /api/v1/gw/static/js/vendor.www_bristol_ac_uk.hHsrG.v1768... | 74.8 KiB | 43.0 KiB |
| /assets/responsive-web-project/2.7.0/js/responsive-web-pr... | 38.5 KiB | 30.0 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| www.bristol.ac.uk/ | 1.8 s | 19 ms | 2.7 ms |
| Unattributable | 1.2 s | 555 ms | 0.0 ms |
| www.googletagmanager.com/gtm.js?id=GTM-MWCJ929 | 633 ms | 508 ms | 92 ms |
| /api/v1/gw/static/js/vendor.www_bristol_ac_uk.hHsrG.v1768... | 612 ms | 403 ms | 1.4 ms |
| app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce?autoBlock=on | 486 ms | 389 ms | 59 ms |
| app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce | 163 ms | 103 ms | 59 ms |
| /assets/responsive-web-project/2.7.0/js/responsive-web-pr... | 128 ms | 48 ms | 2.2 ms |
| www.bristol.ac.uk/assets/homepage-search/1.0.4/js/app.12148122.js | 109 ms | 107 ms | 1.6 ms |
| www.bristol.ac.uk/assets/homepage-search/1.0.4/js/chunk-vendors.a3cb5fa7.js | 83 ms | 45 ms | 29 ms |
| www.bristol.ac.uk/assets/homepage-search/1.0.4/js/chunk-480a6038.24fe62bd.js | 82 ms | 60 ms | 22 ms |
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 2.4 s |
| Other | 1.1 s |
| Style & Layout | 1.1 s |
| Rendering | 379 ms |
| Script Parsing & Compilation | 296 ms |
| Parse HTML & CSS | 97 ms |
| Garbage Collection | 63 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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 dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
We use essential cookies to make our site work. With your consent, we may also … div#termly-code-snippet-support > div > div.termly-styles-root-f9c495 > div.termly-styles-consent-banner-fa199d |
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.
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Skip to site navigation nav > ul.list > li.list__item > a.list__link |
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.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce line 177, col 65403 | Uncaught Error: Termly resource blocker has already been loaded on this page. Check your markup for duplicate <script> tags including https://app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce |
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.
3.61 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.27 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
93 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.271
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.15 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.27 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
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.
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.
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.
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
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Stone buildings, blue sky, green grass, gazebos and people body > main#main > section#homepage-hero > div.hero__image | www.bristol.ac.uk/media-library/sites/homepage/images/homepage-1.jpg | 516.0 KiB | 310.2 KiB |
Members of the public cross a bridge over a river. On the side of the bridge is… div.module > a.module__link > div.module__media > div.module__image | /media-library/sites/aa/images/homepage/bristol-banner-on... | 130.3 KiB | 64.3 KiB |
harbourside with blue sky and boats on the water div.module > a.module__link > div.module__media > div.module__image | www.bristol.ac.uk/media-library/sites/homepage/images/4547_10015456.jpg | 127.5 KiB | 58.9 KiB |
A large body of water with a prominent building with a turret in the forefront.… div.module > a.module__link > div.module__media > div.module__image | www.bristol.ac.uk/media-library/sites/homepage/images/mumbai-homepage-2.jpg | 63.0 KiB | 36.6 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce?autoBlock=on | 143.5 KiB | 871 ms |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| bris.ac.uk/ | 783 ms |
| www.bristol.ac.uk/ | 0.0 ms |
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
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
Open events and virtual visits
Visit us on campus or attend an online event to… body > main#main > section.block | 0.253 |
Open events and virtual visits
Visit us on campus or attend an online event to… body > main#main > section.block > div.container | 0.008 |
Open events and virtual visits
Visit us on campus or attend an online event to… body > main#main > section.block | 0.006 |
Undergraduate open days section#homepage-hero > div.container > div.hero__content > div.hero__main | 0.002 |
Open events and virtual visits
Visit us on campus or attend an online event to… body > main#main > section.block | 0.001 |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /assets/responsive-web-project/2.7.0/css/responsive-web-p... | 146.2 KiB | 121.9 KiB |
| /assets/responsive-web-project/2.7.0/css/responsive-web-p... | 39.6 KiB | 36.8 KiB |
| /*! normalize.css v8.0.1 | MIT License | github.com/necol... | 40.5 KiB | 26.8 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| /api/v1/gw/static/js/main.www_bristol_ac_uk.hHsrG.v176849... | 295.1 KiB | 141.7 KiB |
| www.bristol.ac.uk/assets/homepage-search/1.0.4/js/chunk-480a6038.24fe62bd.js | 136.2 KiB | 94.4 KiB |
| app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce | 143.3 KiB | 82.5 KiB |
| /assets/responsive-web-project/2.7.0/js/responsive-web-pr... | 75.5 KiB | 71.0 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-MWCJ929 | 194.4 KiB | 57.5 KiB |
| app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce?autoBlock=on | 143.3 KiB | 52.8 KiB |
| www.bristol.ac.uk/assets/homepage-search/1.0.4/js/chunk-vendors.a3cb5fa7.js | 123.5 KiB | 46.3 KiB |
| /api/v1/gw/static/js/vendor.www_bristol_ac_uk.hHsrG.v1768... | 74.8 KiB | 43.5 KiB |
| /assets/responsive-web-project/2.7.0/js/responsive-web-pr... | 38.5 KiB | 30.0 KiB |
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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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 dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
We use essential cookies to make our site work. With your consent, we may also … div#termly-code-snippet-support > div > div.termly-styles-root-f9c495 > div.termly-styles-consent-banner-fa199d |
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.
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Skip to site navigation nav > ul.list > li.list__item > a.list__link |
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.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce line 177, col 65403 | Uncaught Error: Termly resource blocker has already been loaded on this page. Check your markup for duplicate <script> tags including https://app.termly.io/resource-blocker/f00d1986-fa46-46cf-a165-30f04408b1ce |
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.
Send Feedback