General Guide: See Global LCP Guide for universal concepts and fixes.
What is LCP?
Largest Contentful Paint measures when the largest content element becomes visible. Google recommends LCP under 2.5 seconds. Google Sites is a fully managed platform with zero server-side control -- you cannot configure caching, CDN, or server settings. All LCP optimization happens through content choices.
Google Sites-Specific LCP Causes
- Uncompressed uploaded images -- Google Sites does not resize or compress images; they serve at original upload dimensions
- Embedded Google Drive content -- Docs, Sheets, Slides, and Forms embedded as iframes load their own heavy JavaScript bundles
- Multiple embedded maps/videos -- each Google Maps or YouTube embed adds 500KB+ of JavaScript
- Section-heavy page layouts -- Google Sites renders each section as a separate layout container, increasing DOM complexity
- Google Fonts loading -- site-wide font selections load multiple weights from Google Fonts CDN
Fixes
1. Compress Images Before Upload
Since Google Sites provides no image processing, optimize before uploading:
# Resize and compress images before uploading to Google Sites
# Target: hero images under 200KB, section images under 100KB
# Using ImageMagick
convert hero.jpg -resize 1920x1080 -quality 75 -strip hero-optimized.jpg
# Using squoosh-cli for WebP (Google Sites supports WebP upload)
npx @nicolo-ribaudo/squoosh-cli --webp '{"quality":80}' -d output/ hero.jpg
Target dimensions for Google Sites:
- Banner/hero images: 1920x1080 max, under 200KB
- Section images: 800x600, under 100KB
- Thumbnail images: 400x300, under 50KB
Upload the compressed versions. Google Sites accepts JPG, PNG, GIF, and WebP.
2. Minimize Embedded Content
Each embed (Docs, Sheets, Maps, YouTube) loads its own JavaScript framework. Reduce embeds on your landing page:
- Replace Google Docs embeds with native Google Sites text blocks -- copy-paste content directly
- Replace Google Sheets embeds with static tables or screenshots for simple data
- Limit YouTube embeds to one per page, or link to YouTube instead of embedding
- Replace Google Maps embeds with a static map image that links to Google Maps
3. Simplify Page Structure
Google Sites renders each section independently. Fewer sections = faster LCP:
- Consolidate multiple small sections into fewer larger ones
- Move heavy content (videos, maps, forms) below the fold
- Use the simplest layout (single column) for above-fold content
- Limit the number of images in the first visible section to 1-2
4. Choose System Fonts
In Google Sites settings, choose fonts that load quickly:
- Default font (Roboto on Google Sites) loads fastest since it may already be cached
- Avoid selecting multiple custom fonts across headers and body text
- Google Sites loads the full font family regardless of which weights you use
5. Optimize for First Section LCP
The first visible section determines LCP. Make it lightweight:
- Use a text-based hero instead of a large background image
- If using a hero image, ensure it is pre-compressed (see step 1)
- Avoid placing embedded content (YouTube, Maps, Forms) in the first section
Measuring LCP on Google Sites
- PageSpeed Insights -- the only reliable tool since Google Sites has no developer console access
- Chrome DevTools Lighthouse -- run on the published site URL (not the editor)
- WebPageTest -- use filmstrip view to see exactly when hero content appears
- Google Search Console -- Core Web Vitals report shows field data for indexed pages
There is no way to view source code, network requests, or server timing in Google Sites' editor. All debugging must happen on the published URL.
Analytics Script Impact
Google Sites does not support custom JavaScript. Analytics options are limited:
- Google Analytics -- add via Settings > Analytics in the Google Sites editor; this loads asynchronously and has minimal LCP impact
- No GTM support -- you cannot add Google Tag Manager or any custom scripts
- No third-party analytics -- Matomo, Hotjar, etc. cannot be installed on Google Sites
This limited analytics surface actually benefits LCP since there are no third-party scripts to contend with.