Performance and Accessibility
Web PerformanceThe Problem
The UMBC.edu homepage had a mobile Largest Contentful Paint of 11.2 seconds. The main content was buried inside a JavaScript bundle, unused CSS was shipping to every page, and scripts blocked rendering. On mobile, the page was effectively unusable for the first several seconds.
What I Did
- Moved the LCP paragraph out of the JavaScript bundle and inlined it as critical HTML content
- Deferred non-essential JavaScript and lazy-loaded below-fold images
- Purged unused CSS by updating Tailwind content globs and removing dead styles
- Audited and optimized third-party script loading order
Results
Mobile LCP
11.2s
3.8s
PageSpeed Accessibility
100
Silktide Compliance
95%
These scores are across the pages built on my custom WordPress theme. The accessibility work connects to a broader commitment. In 2023 I spoke on it twice for CASE: "Accessible Design is Better Design (for everyone)" at the CASE District I & II Annual Conference in March, and "Inclusion in the Digital World" at the CASE All Districts Online Conference in June.