Facebook: impact on page speed
Category: Advertising pixel
The Meta Pixel (formerly Facebook Pixel) tracks page views and conversions for Facebook and Instagram ads. Its script is loaded on every page where the pixel is installed, whether or not a campaign is running.
On 27 % of the 4108 homepages measured, Facebook is among the five heaviest third parties. Where it is, it takes a median of 285 ms of main-thread time; on the heaviest quarter of those sites it takes 370 ms or more.
27 %
of homepages: among the five heaviest third parties
285 ms
median main-thread time
370 ms
main-thread time on the heaviest quarter (p75)
225 KB
median transfer size
Distribution across homepages
Percentiles across 1094 homepages with Facebook.
| Percentile | Main-thread time | Transfer size |
|---|---|---|
| p25 |
213 ms
|
211 KB |
| Median |
285 ms
|
225 KB |
| p75 |
370 ms
|
278 KB |
| p90 |
510 ms
|
315 KB |
In context
By median main-thread time, Facebook ranks seventh of 65 third parties in the benchmark, lighter than Google CDN and heavier than ZenDesk.
On 63 % of the homepages where it appears, Facebook alone uses 250 milliseconds of main-thread time or more, the mark from which Lighthouse flags third-party code.
Homepages with Facebook weigh 5.5 MB at the median (JavaScript: 2.5 MB), homepages without it 3.8 MB (JavaScript: 1.3 MB).
Often loaded together with
Share of homepages with Facebook where the other tool is also among the five heaviest third parties.
- Google Tag Manager 90 %
- TikTok 28 %
- Google/Doubleclick Ads 16 %
How to spot Facebook on your page
The pixel loads fbevents.js from connect.facebook.net, then a configuration file for each pixel ID on the page, and sends its events to facebook.com/tr. Every additional pixel ID, for example from a former agency or a second ad account, adds its own configuration request. Shops that send events through the Conversions API can often keep the browser pixel to a minimal page-view setup.
How to reduce the impact of Facebook
- Load the pixel only after consent and, where possible, after the page has finished loading.
- Use the Conversions API to send events from the server and reduce work in the browser.
- Remove duplicate pixel IDs and pixels of ad accounts that are no longer used.
Frequently asked questions
How can I load Facebook with less impact?
Load the pixel only after consent and, where possible, after the page has finished loading. Use the Conversions API to send events from the server and reduce work in the browser.
Does Facebook affect Core Web Vitals?
The Meta Pixel affects INP rather than LCP or CLS. Its script and the events it sends on page view and on clicks run on the main thread, and when the pixel is combined with consent logic and other ad pixels the work stacks up during the first seconds. It has no visible element, so it does not shift the layout.
Method and sample: Third-Party Benchmark.