Feedback

Google Maps: impact on page speed

Category: Map embed

An interactive Google Map loads the Maps JavaScript and map tiles as soon as it is rendered. On many sites it sits in the footer or on a contact page where most visitors never interact with it.

On 3.2 % of the 5509 homepages measured, Google Maps is among the five heaviest third parties. Where it is, it takes a median of 160 ms of main-thread time; on the heaviest quarter of those sites it takes 212 ms or more.

3.2 %

of homepages: among the five heaviest third parties

160 ms

median main-thread time

212 ms

main-thread time on the heaviest quarter (p75)

371 KB

median transfer size

Distribution across homepages

Percentiles across 179 homepages with Google Maps.

Percentile Main-thread time Transfer size
p25
116 ms
218 KB
Median
160 ms
371 KB
p75
212 ms
386 KB
p90
287 ms
395 KB

In context

By median main-thread time, Google Maps ranks 23rd of 72 third parties in the benchmark, lighter than TikTok and heavier than Google/Doubleclick Ads.

On 15 % of the homepages where it appears, Google Maps alone uses 250 milliseconds of main-thread time or more, the mark from which Lighthouse flags third-party code.

Homepages with Google Maps weigh 5.4 MB at the median (JavaScript: 2.0 MB), homepages without it 4.2 MB (JavaScript: 1.5 MB).

Often loaded together with

Share of homepages with Google Maps where the other tool is also among the five heaviest third parties.

How to spot Google Maps on your page

The Maps JavaScript API loads from maps.googleapis.com, on some sites through the older maps.google.com address, and fetches the map data from there. Store locators that need search and markers justify the interactive map; a single address in the footer usually does not. A static image of the location with a link to Google Maps gives visitors the same information without loading the map engine.

How to reduce the impact of Google Maps

Frequently asked questions

How can I load Google Maps with less impact?

Show a static map image that links to Google Maps, or load the interactive map only on click. Load maps further down the page only when they scroll into view.

Does Google Maps affect Core Web Vitals?

An embedded Google Map is heavy for its size: the interactive map loads tiles, fonts and a large JavaScript bundle. On a contact or location page where the map is visible without scrolling it can delay LCP, and its scripts weigh on INP. A map container without a fixed height shifts everything below it once the map renders.

Method and sample: Third-Party Benchmark.

Run a free test All third parties in the benchmark