Fix guides · Performance

How to fix a slow First Contentful Paint (FCP) and Speed Index

How long visitors stare at a blank screen. The usual causes (slow server, blocking files, web fonts) and how to fix them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.

Time to fix
1–2 hours
Skill needed
Copy and paste
Who notices
Every visitor, most of all on phones

Why it matters

First Contentful Paint (FCP) is when the first text or image appears. Until then, visitors see a blank screen and some leave. On phones, Lighthouse counts 1.8 seconds or less as fast and over 3 seconds as slow.

Speed Index measures how quickly the page fills in visually as it loads. It improves with the same fixes as FCP.

These are summary measures, not causes. A slow FCP almost always comes from one of three things: the server is slow to send the page, files in the <head> block drawing, or text waits for a web font.

“FCP has shown improvements over the past few years. Although there was a slight decline in 2023, the metric recovered in 2024, reaching 68% for desktop and 51% for mobile websites.”

HTTP Archive Web Almanac 2024, Performance

Before you start

  • Look at the other issues in your report first: render-blocking requests, slow server response, font display and request chains each have their own guide, and fixing them is what moves FCP.
  • Lab timings vary between runs. Judge a change by a clear drop across two or three audits, not one number.

Fix it on your platform

Shopify

  1. Remove or defer apps that add scripts to the <head> (Online Store → Themes → Customize → App embeds). Render-blocking stylesheets and scripts in the <head> are the usual reason FCP is late.
  2. In theme code, place your main stylesheet and font preloads above {{ content_for_header }}, so the browser fetches them while Shopify renders the rest of the page.
  3. Fewer fonts help: system fonts need no download at all, and web fonts served from Shopify's CDN avoid connecting to another server.

WordPress

  1. Turn on page caching (a caching plugin, or your host's built-in cache) so the server sends a ready-made page instead of building it on every visit.
  2. Deactivate plugins you don't use; many add stylesheets and scripts to every page.
  3. If your theme loads several Google Fonts weights, trim them to the ones you use.

Webflow

  1. Move third-party scripts in your site and page custom code from the head to the code before </body>, or add defer to them.
  2. Upload fonts as WOFF2 custom fonts instead of linking Google Fonts, and set their font display to swap so text shows while they load.
  3. Remove fade-in interactions on content at the top of the page; it doesn't count as shown while it's invisible.

Wix

  1. Wix caches pages and serves them from a CDN automatically. Leave caching on unless a page needs live data.
  2. Use system fonts where you can and keep to three fonts or fewer per page, as Wix recommends.
  3. Review custom code in Settings → Custom Code, and move code that isn't needed straight away to Body – end.

Squarespace

  1. Use fewer fonts: Squarespace loads every selected font before the page can appear, and suggests no more than two.
  2. Move code from the Header code injection field to the Footer field where you can.
  3. Too many URL redirects can slow pages down; streamline the list in the URL Mappings panel.

Next.js

  1. Render pages statically or cache them where you can, so the server answers quickly.
  2. Load fonts with next/font (it self-hosts them and uses font-display: swap by default) and third-party scripts with next/script.
  3. Avoid hiding page content until client-side JavaScript runs.

Any other site

  1. Defer scripts in the <head>, keep CSS small and avoid @import chains.
  2. Set font-display: swap on web fonts, and serve them from your own domain.
  3. Make sure the server responds quickly and compresses HTML, CSS and JavaScript.

Check that it's fixed

  • Re-run your StudioLNC audit a couple of times and compare FCP and Speed Index with your earlier results.
  • Real-visitor FCP in your Vitals Monitor follows over the next four weeks.

Find every issue like this on your site

Free audit of performance, accessibility, SEO and security, with fixes for your platform.