Skip to content
Audit Complete

Results for https://georgetown.edu

Visit site
Spain Spain · Madrid Completed: Apr 21, 2026 19:47 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)
C73

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

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

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

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

WordPress · 413 peers
You 73
·
Avg 74
At average
0 50 100
Better than 29% of WordPress sites See full WordPress benchmark →
Adobe Fonts · 141 peers
You 73
·
Avg 73
At average
0 50 100
Better than 41% of Adobe Fonts sites See full Adobe Fonts benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

Page weighs 15.3 MB (12.6 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

99 third-party resources (100% 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

3

High impact, low effort — start here.

Strategic

2

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%2Fgeorgetown.edu)](https://beavercheck.com/results/c88c9c33-5cf9-4057-9467-eb9f85043da6)
<a href="https://beavercheck.com/results/c88c9c33-5cf9-4057-9467-eb9f85043da6"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgeorgetown.edu" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fgeorgetown.edu

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 25.5s 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.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 25.5s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

3 critical 5 warning

8 barrier(s) likely increasing bounce by ~34%.

Speed (2)

Page takes 25.5s to load

+12% bounce

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

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

Page feels frozen for 870ms

+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 (3)

Mixed content on HTTPS page

+8% bounce

Browsers block insecure subresources — broken images, missing scripts, warning badge

Fix: Change http:// URLs inside the page to https:// (or protocol-relative)

No HSTS header

+1% bounce

Returning 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% 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 (1)

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)

No skip-to-content link

+1% bounce

Keyboard 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

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

$550 investment → $3.17/month returns + USD 157,500 risk avoided

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

Investment

$550

6h · 5 findings

Monthly returns

$3.17 /mo

~$38 / year

  • Bandwidth savings $3.17

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

$150 — 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.

Full methodology & sources

Estimated Remediation Cost

$550

5.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,128 / month at risk

~$157,538 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+2 more

Bandwidth Waste

$3.17 /mo

39586.5 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~4.0 MB per page load
    Saves $3.17/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 4 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.

36
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
88
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
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.

6.34 s

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

25.49 s

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

870 ms

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

0.000

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

11.42 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.

26.25 s

Detailed Report

Audit breakdown by category with detailed findings.

36

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 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.

RequestCache TTLTransfer Size
www.juicer.io/api/media/27229307?s=60ad2558c3e6c978c3100726de4cc792f7017b961209600.0 s1.0 MiB
www.juicer.io/embed-no-jquery.js3600.0 s118.8 KiB
www.juicer.io/api/media/28082764?s=7db95d9c4ca2972f00c391055be051eec5f3dd931209600.0 s688.6 KiB
www.juicer.io/api/media/27309542?s=1e315d2c6332d4d3bfafaed6846ea273c5e0ca641209600.0 s656.8 KiB
www.juicer.io/api/media/25160445?s=6ea37aaba67f66f333855e134aac39e097c9c91d1209600.0 s342.2 KiB
www.juicer.io/api/media/26937023?s=7ba84b699a2d0ce83da1f089ccba360d9c2674751209600.0 s287.4 KiB
www.juicer.io/api/media/26553288?s=be2636776a95b2204cd4e07c643a6cd036f9dc191209600.0 s225.2 KiB
www.juicer.io/api/media/25754192?s=b9b41a92f6a69b3a9a8b4ca11f77c0badfad30c01209600.0 s192.0 KiB
www.juicer.io/api/media/25240287?s=f9039b19ea09b4d89ba2b3da122e0b1c6e34447f1209600.0 s173.6 KiB
www.juicer.io/embed.css3600.0 s16.1 KiB
www.juicer.io/api/media/26486368?s=2a82ac2ac11c8e0387f780bf570fb9edd5b63d421209600.0 s99.5 KiB
www.juicer.io/api/media/24559784?s=b2bf2661e438fbb76038eb52a7bad121e7c1f86e1209600.0 s88.7 KiB
www.juicer.io/api/media/26829777?s=4ec657815a18740960828f5f199595617c8c2a131209600.0 s85.5 KiB
assets.juicer.io/standalone-sprites/gallery-left.png3600.0 s9.9 KiB
assets.juicer.io/standalone-sprites/gallery-right.png3600.0 s9.9 KiB
assets.juicer.io/fonts/fontawesome-5-juicer.woff2?833615223600.0 s9.6 KiB
assets.juicer.io/standalone-sprites/gallery.png3600.0 s9.5 KiB
www.juicer.io/api/media/28220707?s=34f843d106790e302b3788f7a234890b5f3d8f831209600.0 s46.5 KiB
assets.juicer.io/standalone-sprites/twitter-retweet-gray.png3600.0 s4.4 KiB
assets.juicer.io/standalone-sprites/twitter-reply-gray.png3600.0 s4.2 KiB
assets.juicer.io/standalone-sprites/twitter-like-gray.png3600.0 s4.1 KiB
/embed/8825331245-8d5fed37-9653-41a4-9783-88916ecc4fef/wp...600.0 s1.5 KiB
static.addtoany.com/menu/page.js?ver=1.0.33886400.0 s2.2 KiB
/api/posts/507328212/poster_images.jpg?external_id=204519...1209600.0 s7.7 KiB
/api/posts/506323328/poster_images.jpg?external_id=203500...1209600.0 s7.6 KiB
/api/posts/506599756/poster_images.jpg?external_id=203766...1209600.0 s7.6 KiB
/api/posts/505775613/poster_images.jpg?external_id=202921...1209600.0 s7.4 KiB
/api/posts/506092947/poster_images.jpg?external_id=203245...1209600.0 s7.4 KiB
/api/posts/506624962/poster_images.jpg?external_id=203828...1209600.0 s7.4 KiB
/api/posts/506910977/poster_images.jpg?external_id=204117...1209600.0 s7.4 KiB
/api/posts/506749757/poster_images.jpg?external_id=203940...1209600.0 s7.3 KiB
/api/posts/506794346/poster_images.jpg?external_id=203949...1209600.0 s7.2 KiB
/api/posts/506056664/poster_images.jpg?external_id=203210...1209600.0 s7.2 KiB
/api/posts/507273991/poster_images.jpg?external_id=204477...1209600.0 s7.1 KiB
/api/posts/506949691/poster_images.jpg?external_id=204160...1209600.0 s7.1 KiB
/p.css?s=1&k=qbp1quu&ht=tk&f=8482.8483.8484.8485.8486.848...604800.0 s172 B

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:45.651 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
Photo from Georgetown on Twitter at 4/16/26 at 2:00PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/28082764?s=7db95d9c4ca2972f00c391055be051eec5f3dd93687.4 KiB678.1 KiB
Photo from Georgetown on Twitter at 4/7/26 at 8:04PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/27309542?s=1e315d2c6332d4d3bfafaed6846ea273c5e0ca64655.6 KiB646.2 KiB
Skyline of Georgetown&#039;s campus and Healy Hall towers behind Key Bridge at … div.single-image > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2022/10/20180920_GeorgetownSunsetStoc...524.8 KiB483.4 KiB
div.c--component > div.f--field > div.image-field-wrapper > img div.c--component > div.f--field > div.image-field-wrapper > img
www.georgetown.edu/wp-content/uploads/2025/06/6K1A9080-resized-1920x1080.jpg164.2 KiB158.9 KiB
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2025/06/IS9A9061-select-scaled-2000x1...125.9 KiB120.6 KiB
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2023/08/Community-scholars-program-ch...70.2 KiB67.2 KiB
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2025/06/IS9A6932-scaled-2000x1500-c-d...65.7 KiB62.9 KiB
USILA National Team of the Week - Rory Connor - 041526 li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/28220707?s=34f843d106790e302b3788f7a234890b5f3d8f8346.3 KiB38.9 KiB
Young man holds cross while processing out of a chapel div.c--component > div.f--field > div.image-field-wrapper > img
www.georgetown.edu/wp-content/uploads/2026/04/20250419-Ministry_1127-420x280.jpg27.3 KiB14.5 KiB
Next div.j-text > a.j-image > span.j-gallery-nav > span.j-gallery-arrow
assets.juicer.io/standalone-sprites/gallery-right.png9.6 KiB9.5 KiB
Previous div.j-text > a.j-image > span.j-gallery-nav > span.j-gallery-arrow
assets.juicer.io/standalone-sprites/gallery-left.png9.6 KiB9.5 KiB
li.feed-item > div.j-text > a.j-image > ::after li.feed-item > div.j-text > a.j-image > ::after
assets.juicer.io/standalone-sprites/gallery.png9.1 KiB9.0 KiB
Profile image for Georgetown li.feed-item > div.j-poster > a > img
/api/posts/507328212/poster_images.jpg?external_id=204519...7.0 KiB6.9 KiB
Profile image for Georgetown li.feed-item > div.j-poster > a > img
/api/posts/507273991/poster_images.jpg?external_id=204477...7.0 KiB6.9 KiB
Profile image for Georgetown li.feed-item > div.j-poster > a > img
/api/posts/506949691/poster_images.jpg?external_id=204160...7.0 KiB6.9 KiB

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-4-IMG
nodeLabel: div.swiper-slide > div.f--field > div.image-field-wrapper > img
path: 4,HTML,2,BODY,0,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,SECTION,0,DIV,0,ARTICLE,0,DIV,0,DIV,4,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.swiper-slide > div.f--field > div.image-field-wrapper > img
snippet: <img decoding="async" src="https://www.georgetown.edu/wp-content/uploads/2025/06/IS9A9061-select-scal…" alt="" role="presentation">

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

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.

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

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: 754 ms
URLTime Spent
georgetown.edu/754 ms
www.georgetown.edu/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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 320 ms 13.2 KiB
URLTransfer SizeEst Savings
/wp-content/themes/georgetown/pattern_lab/source/css/styl...77.3 KiB13.2 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.

Estimated savings: 830 ms 85.1 KiB
URLTransfer SizeEst Savings
/wp-content/themes/georgetown/pattern_lab/source/css/styl...77.1 KiB70.7 KiB
www.juicer.io/embed.css15.7 KiB14.5 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 Evaluation2.0 s
Other904 ms
Style & Layout445 ms
Script Parsing & Compilation350 ms
Parse HTML & CSS94 ms
Rendering68 ms
Garbage Collection50 ms

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
Photo from Georgetown on Twitter at 3/12/26 at 2:30PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/25160445?s=6ea37aaba67f66f333855e134aac39e097c9c91d
Photo from Georgetown on Twitter at 4/6/26 at 3:08PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/27229307?s=60ad2558c3e6c978c3100726de4cc792f7017b96
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2025/06/IS9A9061-select-scaled-2000x1...
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2023/08/Community-scholars-program-ch...
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2025/06/IS9A6932-scaled-2000x1500-c-d...
Photo from Georgetown on Twitter at 3/27/26 at 11:05PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/26486368?s=2a82ac2ac11c8e0387f780bf570fb9edd5b63d42
Photo from Georgetown on Twitter at 3/13/26 at 1:55PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/25240287?s=f9039b19ea09b4d89ba2b3da122e0b1c6e34447f
Photo from Georgetown on Twitter at 3/29/26 at 4:11PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/26553288?s=be2636776a95b2204cd4e07c643a6cd036f9dc19
Photo from Georgetown on Twitter at 3/20/26 at 2:46PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/25754192?s=b9b41a92f6a69b3a9a8b4ca11f77c0badfad30c0
Photo from Georgetown on Twitter at 4/2/26 at 12:00AM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/26937023?s=7ba84b699a2d0ce83da1f089ccba360d9c267475
Photo from Georgetown on Twitter at 4/7/26 at 8:04PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/27309542?s=1e315d2c6332d4d3bfafaed6846ea273c5e0ca64
Photo from Georgetown on Twitter at 4/16/26 at 2:00PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/28082764?s=7db95d9c4ca2972f00c391055be051eec5f3dd93
USILA National Team of the Week - Rory Connor - 041526 li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/28220707?s=34f843d106790e302b3788f7a234890b5f3d8f83
2025-26 Women's Team li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/26829777?s=4ec657815a18740960828f5f199595617c8c2a13
Photo from Georgetown on Twitter at 3/4/26 at 3:00PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/24559784?s=b2bf2661e438fbb76038eb52a7bad121e7c1f86e

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

Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
User Timing marks and measures 22 user timings
Avoid long main-thread tasks 13 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 230 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
88

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Close the Search Dialog body.home > div.lc--layout-container > div.l--layout > div#search-form

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
An Education That Matters div.c--component > div.text-container > div.f--field > h3

These are opportunities to improve keyboard navigation in your application.

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
Georgetown University @Georgetown X (Twitter) Logo USILA National Team of the W… section.cc--component-container > div.c--component > div.currator-feed > ul.juicer-feed

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Georgetown University @Georgetown X (Twitter) Logo USILA National Team of the W… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo 2025-26 Women's Team The Ge… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item

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
`[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
Background and foreground colors have a sufficient contrast ratio
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[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
`<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.
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.
96

Best Practices

General

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 find a valid digest in the 'integrity' attribute for resource 'https://static.addtoany.com/menu/page.js?ver=1.0.338' with computed SHA-512 integrity 'cTTpgjNtPcn/54j5hJuiINRWiX7yMWXQQNpf6EOYRk6UrhXyQJCkkWSvZ5ZPOWmQKHSmS0dQ3iuY0PIYB6V+lg=='. The resource has been blocked.
Uses HTTPS
Avoids deprecated APIs
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
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
Use a strong HSTS policy
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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

73
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
84
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
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.

1.10 s

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

3.67 s

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

46 ms

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

0.003

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

2.43 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.

3.75 s

Detailed Report

Audit breakdown by category with detailed findings.

73

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:38.016 source:map[type:text value:[unattributed]]] map[reflowTime:15.019 source:map[column:85575 line:1 type:source-location url:https://www.georgetown.edu/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]]]

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
Skyline of Georgetown&#039;s campus and Healy Hall towers behind Key Bridge at … div.single-image > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2022/10/20180920_GeorgetownSunsetStoc...524.8 KiB413.6 KiB
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2025/06/IS9A9061-select-scaled-2000x1...125.9 KiB100.4 KiB
div.c--component > div.f--field > div.image-field-wrapper > img div.c--component > div.f--field > div.image-field-wrapper > img
www.georgetown.edu/wp-content/uploads/2025/06/6K1A9080-resized-1920x1080.jpg164.2 KiB83.0 KiB
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2023/08/Community-scholars-program-ch...70.2 KiB56.0 KiB
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2025/06/IS9A6932-scaled-2000x1500-c-d...65.7 KiB52.4 KiB
Young man holds cross while processing out of a chapel div.c--component > div.f--field > div.image-field-wrapper > img
www.georgetown.edu/wp-content/uploads/2026/04/20250419-Ministry_1127-420x280.jpg27.3 KiB23.1 KiB
A doctor in a white lab coat smiles in front of a desk div.c--component > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2026/04/Dr.-Marc-Lippman-Portrait-1-4...15.1 KiB11.2 KiB
A woman with red hair and a maroon top smiles in front of a bookshelf div.c--component > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2026/04/McNamer-GU-headshot-copy-scal...10.1 KiB7.5 KiB

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-8-VIDEO
nodeLabel: div.swiper-slide > div.slide-image > div.f--field > video
path: 4,HTML,2,BODY,0,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,SECTION,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,SECTION,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.swiper-slide > div.slide-image > div.f--field > video
snippet: <video role="presentation" tabindex="-1" autoplay="" loop="" playsinline="" muted="">

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

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.

RequestCache TTLTransfer Size
www.juicer.io/api/media/27229307?s=60ad2558c3e6c978c3100726de4cc792f7017b961209600.0 s1.0 MiB
www.juicer.io/embed-no-jquery.js3600.0 s118.8 KiB
www.juicer.io/api/media/28082764?s=7db95d9c4ca2972f00c391055be051eec5f3dd931209600.0 s688.3 KiB
www.juicer.io/api/media/27309542?s=1e315d2c6332d4d3bfafaed6846ea273c5e0ca641209600.0 s656.8 KiB
www.juicer.io/api/media/25160445?s=6ea37aaba67f66f333855e134aac39e097c9c91d1209600.0 s342.2 KiB
www.juicer.io/api/media/26937023?s=7ba84b699a2d0ce83da1f089ccba360d9c2674751209600.0 s287.4 KiB
www.juicer.io/api/media/26553288?s=be2636776a95b2204cd4e07c643a6cd036f9dc191209600.0 s225.2 KiB
www.juicer.io/api/media/25754192?s=b9b41a92f6a69b3a9a8b4ca11f77c0badfad30c01209600.0 s191.8 KiB
www.juicer.io/api/media/25240287?s=f9039b19ea09b4d89ba2b3da122e0b1c6e34447f1209600.0 s173.2 KiB
www.juicer.io/embed.css3600.0 s16.1 KiB
www.juicer.io/api/media/26486368?s=2a82ac2ac11c8e0387f780bf570fb9edd5b63d421209600.0 s99.5 KiB
www.juicer.io/api/media/24559784?s=b2bf2661e438fbb76038eb52a7bad121e7c1f86e1209600.0 s88.6 KiB
www.juicer.io/api/media/26829777?s=4ec657815a18740960828f5f199595617c8c2a131209600.0 s85.3 KiB
assets.juicer.io/standalone-sprites/gallery-right.png3600.0 s10.2 KiB
assets.juicer.io/standalone-sprites/gallery-left.png3600.0 s9.9 KiB
assets.juicer.io/fonts/fontawesome-5-juicer.woff2?833615223600.0 s9.6 KiB
assets.juicer.io/standalone-sprites/gallery.png3600.0 s9.5 KiB
www.juicer.io/api/media/28220707?s=34f843d106790e302b3788f7a234890b5f3d8f831209600.0 s46.6 KiB
assets.juicer.io/standalone-sprites/twitter-reply-gray.png3600.0 s4.2 KiB
assets.juicer.io/standalone-sprites/twitter-retweet-gray.png3600.0 s4.1 KiB
assets.juicer.io/standalone-sprites/twitter-like-gray.png3600.0 s4.1 KiB
/embed/8825331245-8d5fed37-9653-41a4-9783-88916ecc4fef/wp...600.0 s1.5 KiB
static.addtoany.com/menu/page.js?ver=1.0.33886400.0 s2.2 KiB
/api/posts/507328212/poster_images.jpg?external_id=204519...1209600.0 s7.5 KiB
/api/posts/506323328/poster_images.jpg?external_id=203500...1209600.0 s7.5 KiB
/api/posts/506056664/poster_images.jpg?external_id=203210...1209600.0 s7.4 KiB
/api/posts/506624962/poster_images.jpg?external_id=203828...1209600.0 s7.4 KiB
/api/posts/505775613/poster_images.jpg?external_id=202921...1209600.0 s7.4 KiB
/api/posts/506910977/poster_images.jpg?external_id=204117...1209600.0 s7.4 KiB
/api/posts/507273991/poster_images.jpg?external_id=204477...1209600.0 s7.3 KiB
/api/posts/506794346/poster_images.jpg?external_id=203949...1209600.0 s7.3 KiB
/api/posts/506749757/poster_images.jpg?external_id=203940...1209600.0 s7.1 KiB
/api/posts/506599756/poster_images.jpg?external_id=203766...1209600.0 s7.1 KiB
/api/posts/506092947/poster_images.jpg?external_id=203245...1209600.0 s7.1 KiB
/api/posts/506949691/poster_images.jpg?external_id=204160...1209600.0 s7.1 KiB
/p.css?s=1&k=qbp1quu&ht=tk&f=8482.8483.8484.8485.8486.848...604800.0 s172 B

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.

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: 241 ms
URLTime Spent
georgetown.edu/241 ms
www.georgetown.edu/0.0 ms

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: 50 ms 81.5 KiB
URLTransfer SizeEst Savings
/wp-content/themes/georgetown/pattern_lab/source/css/styl...77.0 KiB67.0 KiB
www.juicer.io/embed.css15.7 KiB14.5 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

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: 0.0 ms 13.2 KiB
URLTransfer SizeEst Savings
/wp-content/themes/georgetown/pattern_lab/source/css/styl...77.4 KiB13.2 KiB

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
Photo from Georgetown on Twitter at 3/12/26 at 2:30PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/25160445?s=6ea37aaba67f66f333855e134aac39e097c9c91d
Photo from Georgetown on Twitter at 4/6/26 at 3:08PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/27229307?s=60ad2558c3e6c978c3100726de4cc792f7017b96
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2025/06/IS9A9061-select-scaled-2000x1...
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2023/08/Community-scholars-program-ch...
div.swiper-slide > div.f--field > div.image-field-wrapper > img div.swiper-slide > div.f--field > div.image-field-wrapper > img
/wp-content/uploads/2025/06/IS9A6932-scaled-2000x1500-c-d...
Photo from Georgetown on Twitter at 3/27/26 at 11:05PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/26486368?s=2a82ac2ac11c8e0387f780bf570fb9edd5b63d42
Photo from Georgetown on Twitter at 3/13/26 at 1:55PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/25240287?s=f9039b19ea09b4d89ba2b3da122e0b1c6e34447f
Photo from Georgetown on Twitter at 3/29/26 at 4:11PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/26553288?s=be2636776a95b2204cd4e07c643a6cd036f9dc19
Photo from Georgetown on Twitter at 3/20/26 at 2:46PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/25754192?s=b9b41a92f6a69b3a9a8b4ca11f77c0badfad30c0
Photo from Georgetown on Twitter at 4/2/26 at 12:00AM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/26937023?s=7ba84b699a2d0ce83da1f089ccba360d9c267475
Photo from Georgetown on Twitter at 4/7/26 at 8:04PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/27309542?s=1e315d2c6332d4d3bfafaed6846ea273c5e0ca64
Photo from Georgetown on Twitter at 4/16/26 at 2:00PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/28082764?s=7db95d9c4ca2972f00c391055be051eec5f3dd93
USILA National Team of the Week - Rory Connor - 041526 li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/28220707?s=34f843d106790e302b3788f7a234890b5f3d8f83
2025-26 Women's Team li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/26829777?s=4ec657815a18740960828f5f199595617c8c2a13
Photo from Georgetown on Twitter at 3/4/26 at 3:00PM li.feed-item > div.j-text > a.j-image > img.j-content-image
www.juicer.io/api/media/24559784?s=b2bf2661e438fbb76038eb52a7bad121e7c1f86e

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

Max Potential First Input Delay 70 ms
Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
User Timing marks and measures 22 user timings
JavaScript execution time 0.5 s
Minimizes main-thread work 1.0 s
Avoid long main-thread tasks 4 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 260 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
84

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
Hilltop Campus div.c--component > div.pane-tabs > div.pane-tabs-inner > div#tab-1-k6894
Capitol Campus div.c--component > div.pane-tabs > div.pane-tabs-inner > div#tab-2-k6894

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Close the Search Dialog body.home > div.lc--layout-container > div.l--layout > div#search-form

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
An Education That Matters div.c--component > div.text-container > div.f--field > h3

These are opportunities to improve keyboard navigation in your application.

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
Georgetown University @Georgetown X (Twitter) Logo USILA National Team of the W… section.cc--component-container > div.c--component > div.currator-feed > ul.juicer-feed

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Georgetown University @Georgetown X (Twitter) Logo USILA National Team of the W… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-1 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo 2025-26 Women's Team The Ge… div.j-stacker-wrapper > div.j-stacker > div#j-column-1 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-1 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-2 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-2 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-2 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-3 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-3 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-3 > li.feed-item

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
`[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
Background and foreground colors have a sufficient contrast ratio
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[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.
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.
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.
96

Best Practices

General

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 find a valid digest in the 'integrity' attribute for resource 'https://static.addtoany.com/menu/page.js?ver=1.0.338' with computed SHA-512 integrity 'cTTpgjNtPcn/54j5hJuiINRWiX7yMWXQQNpf6EOYRk6UrhXyQJCkkWSvZ5ZPOWmQKHSmS0dQ3iuY0PIYB6V+lg=='. The resource has been blocked.
Uses HTTPS
Avoids deprecated APIs
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
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
Use a strong HSTS policy
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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
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