The new Growth Marketing Lead will own paid ads, SEO and content. Every click they buy lands on pages that are built against them: the same 507 KB image is written into the homepage code twice as base64 text, making the HTML alone 1.3 MB, and every other page carries about 1.1 MB of it. Google PageSpeed scores the homepage 57 on mobile and 42 on desktop, with 18.3 MB downloaded and the main content showing after 5.5 to 7 seconds in the lab. Real visitors still pass Core Web Vitals, so this is not an emergency; it is a cheap fix that makes every paid and organic click land faster and lets search engines read a page in kilobytes, not megabytes.
First action
Find the component that inlines the 3,200 x 1,680 image and swap it for an image file.
How to measure it
Homepage download size
- Now
- –
- Target
- under 3 MB
- By
- 30 days
Steps
Find the image
Locate the shared component with the inlined base64 picture (it appears twice).
Front-end developer 2 hours
Replace it
Serve it as a resized WebP or AVIF file, or an SVG.
Front-end developer 4 hours
Compress the rest
Resize and compress the largest content-system images.
Front-end developer 1 day
Lazy-load
Below-the-fold images and videos load on scroll.
Front-end developer 4 hours
Re-test
PageSpeed on homepage, Tower and a case study.
Growth Marketing Lead 1 hour
Set a budget
Page-weight check before each campaign launch.
Growth Marketing Lead ongoing
Why it works
Move the inlined picture to a normal image file served from the image CDN (or replace it with a light SVG), resized to the size it is shown at. Then compress the largest images from the content system, lazy-load anything below the first screen, and set a page budget (for example under 3 MB) that the Growth Marketing Lead checks before each campaign launch.
Landing-page speed lifts paid conversion and Quality Score, and a smaller page is crawled and parsed more reliably. It takes a developer a day and helps every page at once because the image sits in the shared layout.
Ready to use
ChecklistKargo page-weight fix list
[ ] Remove the twice-inlined 507 KB base64 image from the shared layout [ ] Serve it as a resized WebP/AVIF file [ ] Compress the 10 largest content-system images [ ] Lazy-load below-the-fold media [ ] Re-run PageSpeed (mobile and desktop) [ ] Homepage under 3 MB, HTML under 150 KB [ ] Add the check to the campaign launch list
Risks and how to handle them
Visual change to the hero
Compare screenshots before and after.
Regressions from new pages
Add the page-weight check to the launch list.
Evidence
- HiringGrowth Marketing Lead (San Francisco or Atlanta, OTE $180,000-$200,000): "Own and execute Kargo's growth marketing strategy across the full customer lifecycle"; "Manage and improve the performance of digital marketing channels, including paid ads, SEO, content and social media"; "Manage HubSpot Marketing and Sales Hubs"; "Own and execute best in class Account Based Marketing programs"; SQL or Python expected.Source
- Your websitePage size check (November 4, 2026): the homepage HTML is 1.3 MB because the same 507 KB image (a 3,200 x 1,680 picture) is written into the page twice as inline base64 code. Every other page checked (careers, about, Tower, Lift, how it works) is about 1.1 MB of HTML and the blog index 1.35 MB, while the two newest case study articles are about 47 KB.Source
- Google PageSpeedGoogle PageSpeed, homepage: mobile performance 57 and desktop 42; largest content appears after 5.5 seconds on a phone and 7.0 seconds on desktop in the lab; the page downloads 18.3 MB in 169 requests, 12.9 MB of it images from the content system in 57 requests. Real Chrome visitors still pass Core Web Vitals (largest content 2.3 seconds, interaction 117 ms).Source