Optimize website performance using Google PageSpeed recommendations #136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Implements PageSpeed optimizations across all site pages to reduce render-blocking resources, improve resource loading priority, and enhance caching.
deferto all footer scripts (6 files) - eliminates render-blocking while preserving execution orderfetchpriority="high"+ eager loading for hero banners, async decoding throughoutevent.waitUntil(), version bump to v2Files modified:
_includes/footer.html,_includes/head.html,_includes/tiles.html,_layouts/{page,mdpage,news}.html,sw.jsCoverage: All 10 HTML pages optimized with consistent defer (8+), lazy/eager loading, preload hints (4), and fetchpriority on banner images.
Preview Artifact
This PR triggers the
Preview Buildworkflow.Download the
preview-siteartifact from the workflow run to inspect the generated site.To view locally: Extract the artifact and serve it with a local web server:
Then browse to
http://localhost:8000Note: Opening HTML files directly (
file://) won't work correctly due to absolute paths.Internal and external link check logs are in the
preview-link-check-logsartifact.Link checks are non-blocking; fix issues where practical before merge.
Image & Asset Guidelines
Only WebP images should be referenced in the site; originals (PNG/JPG/etc.) may be stored for provenance.
Always reference the
.webpversion in Markdown/HTML.Originals can live alongside WebP conversions but must NOT be used directly in content.
Prefer descriptive, kebab-case filenames (e.g.,
joao-victor-paim.webp).If adding a new image, convert to WebP first. Example conversion commands:
Run the existing resize helper if appropriate:
(Ensure the script suits the new image before relying on it.)
Checks Before Requesting Review
bundle exec jekyll build).Follow-up / Deployment Notes
Users may need hard refresh (Ctrl+Shift+R) on first visit post-deploy to update from service worker v1 → v2. Cache cleanup is automatic.
Screenshots (If UI/Content Changes)
No visual changes - performance optimizations only. Validate via PageSpeed Insights post-deployment.
Maintainers: Ensure branch protection requires only CI + Preview jobs, not production Pages deployment for PRs.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
pagespeed.web.dev/usr/bin/curl curl -s REDACTED(dns block)www.googleapis.com/usr/bin/curl curl -s REDACTED --64 -o em.o /tmp/ccX0PZZk.s(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.