The typeface you choose is not a ranking factor. Google does not assess whether your site uses Lato or Merriweather, and no family is more "SEO friendly" than another. What moves the numbers is the file: how many kilobytes the browser downloads, when the text appears while the font is still on its way, and whether a person can read that text on a six-inch screen in sunlight.
To write this page we measured two things that nobody on page one measures: the real weight of fifteen popular fonts, downloading them one by one, and the typographic setup of nine pages ranking on Google UK.
What Google said, and when
The official answer exists and it has a date. On 26 May 2020, on Twitter, Google's John Mueller replied to someone asking which fonts were best for ranking: "The choice of font doesn't matter for SEO. Use one that works for your site". The quote was picked up by Barry Schwartz on Search Engine Roundtable, and Google has never corrected it since.
In the same exchange Mueller added the part almost nobody quotes: anything you put on your pages can affect their speed. That is where typography really enters the ranking factors, not as style but as a resource to download.
How much a font really weighs: fifteen families measured
The figure missing everywhere is the simplest one: how many kilobytes a font costs. On 20 September 2026 we requested weight 400 of fifteen of the most used families from Google Fonts, isolated the Latin subset file in WOFF2 format (the one a browser actually downloads on an English-language site) and weighed it. None of the files measured is a variable font: they are all static instances, so the comparison is like for like.
| Family | File size (KB) | Ratio to the lightest |
|---|---|---|
| Poppins | 7.7 | 1.0x |
| Oswald | 12.0 | 1.6x |
| Noto Sans | 12.8 | 1.7x |
| Roboto Slab | 13.6 | 1.8x |
| Source Sans 3 | 15.3 | 2.0x |
| Nunito | 15.9 | 2.1x |
| Open Sans | 18.2 | 2.4x |
| Montserrat | 18.3 | 2.4x |
| Work Sans | 19.4 | 2.5x |
| Playfair Display | 21.3 | 2.8x |
| Roboto | 21.4 | 2.8x |
| Raleway | 21.9 | 2.8x |
| Lato | 23.0 | 3.0x |
| Inter | 23.1 | 3.0x |
| Merriweather | 48.0 | 6.2x |
There are 40 KB between Poppins and Merriweather for a single weight. A site using two families with three weights each can go from about 45 KB to almost 290 KB of typography alone, before a single line of HTML. It is a margin nobody claws back by compressing images.
The number has to be read together with a technical detail that changes everything: Google Fonts also declares the Cyrillic, Greek, Vietnamese and latin-ext subsets in its CSS, but the browser only downloads the ones needed for the characters on the page. For an English-language site that is almost always Latin alone. When you read that a family "weighs 300 KB", you are reading the sum of every alphabet, not what your users pay.
The three points where typography touches the numbers
The font delays the text appearing
A web font is a file the browser only discovers after reading the CSS, so late. While downloading it, the browser has to decide what to show, and that decision is made by the font-display property. Google's documentation on web.dev gives each value a precise block period: block keeps the text invisible for 2 to 3 seconds, swap for 0 milliseconds, fallback and optional for 100 milliseconds.
In practice: without font-display: swap, the paragraph that should earn you your Largest Contentful Paint stays blank until the font arrives. The good LCP threshold is 2.5 seconds measured at the 75th percentile of visits, as set out in the official definition of Core Web Vitals. Three seconds of blocking eat it entirely. We have written about this in detail in our guide to Core Web Vitals thresholds and the one on page speed.
The font shifts the layout while the user is reading
With swap, the text appears straight away in the system font and is replaced when the web font arrives. If the two typefaces have different proportions, the paragraph reflows under the fingers of someone who is already reading. That is Cumulative Layout Shift, and the good threshold is 0.1. The countermeasure is on the same web.dev pages: size-adjust, ascent-override and descent-override on the fallback font, so that the temporary typeface takes up the same space as the final one.
The font decides whether the text can be read
UK adults spend four and a half hours a day online, and smartphones account for 75% of that time for men and 79% for women, according to Ofcom's Online Nation 2025 report (data for May 2025). A 13-pixel body size chosen while looking at a 27-inch monitor is almost always read on a pocket screen, often on the move.
Here there are written thresholds, not opinions. WCAG criterion 1.4.3 requires a contrast ratio of at least 4.5:1 between text and background for body text, 3:1 for large text. WCAG criterion 1.4.4 requires that text can be resized up to 200% without loss of content or functionality. These are the two points that light grey on white, so fashionable in redesigns, breaks most consistently. The link to rankings is indirect but real, and we analysed it in the article on user experience optimisation.
What we found measuring nine UK pages
On 26 September 2026 we took the nine organic results ranking on Google UK for a high-volume commercial query, "best mattress" (14,800 searches a month in the UK according to DataForSEO), downloaded their HTML and linked stylesheets, and counted three things: how many families they declare in @font-face, which font-display value they use, and whether the files come from Google's servers or from the site's own domain. The sample includes The Guardian, Expert Reviews, Dreams, Amazon, Sleep Foundation and four mattress retailers.
- Seven pages out of nine declare
font-display: swapat least once. Of the other two, Amazon declares twenty@font-facerules for its own Amazon Ember typeface without anyfont-displayvalue, and Sleep Foundation declares no web fonts at all in the files we downloaded. - Only two pages out of nine load fonts from Google's servers: Expert Reviews through fonts.googleapis.com, and Land of Beds, which caches Google's CSS inline but still pulls the files from fonts.gstatic.com. The other six that use web fonts serve them from their own domain or CDN.
- The number of declared family names ranges from 0 to 6. The Guardian declares six names for its own proprietary typefaces; MattressOnline also reaches six, because Poppins, Rubik and an icon font each come with a separate fallback declaration.
The second figure is the most interesting, because it runs against the global average. The Fonts chapter of the Web Almanac 2025, which analyses millions of pages through HTTP Archive, reports that Google Fonts is present on 54% of desktop sites and 47% of mobile ones, and that about 72% of sites serve at least one font file from their own origin. In our UK sample, self-hosting is the norm, and when we ran the same test on nine Italian pages, eight out of nine self-hosted. Nine pages do not prove a national trend. Part of the explanation is simple: The Guardian, Amazon, Dreams and MattressNextDay use licensed typefaces that are not on Google Fonts and have to be served from their own servers. The other part is probably the European legal issue we cover two sections below.
The other figures in the same chapter help you see where you stand compared with everyone else: web fonts are present on 88% of sites (87% in 2024), font-display: swap appears on 49.6% of desktop pages and 50.1% of mobile ones, the median file weighs between 35 and 36 KB, and variable fonts have reached 39.4% of desktop sites.
On our own site the situation is as follows, and we report it because the method is more useful than the result. The Visilay theme declares twelve WOFF2 files of Lato (six weights, each in a latin and a latin-ext version), 162.4 KB in total. Blog pages preload two of them: lato-400-latin.woff2 at 23 KB and lato-900-latin.woff2 at 22 KB. The real cost on the critical path is therefore 45 KB, not 162. The gap between declared weight and downloaded weight is the point almost every typography audit gets wrong.
Typography is also a legal requirement
This part is missing from the US-centred results that dominate the topic. In the UK, the Equality Act 2010 requires service providers to make reasonable adjustments for disabled people, online as well as offline, and public sector websites have had to meet WCAG since the 2018 accessibility regulations. For anyone selling into the EU there is also a date: Directive 2019/882, the European Accessibility Act, has applied since 28 June 2025 to economic operators placing the covered products and services on the EU market, UK businesses included when they sell there.
Those services include e-commerce. Article 2(2)(f) of the directive defines it as services provided at a distance, through websites and mobile applications, by electronic means, at the individual request of a consumer, with a view to concluding a consumer contract. If you sell online to consumers in the EU, body text size, contrast and resizable text are no longer design choices: they are requirements with an authority checking them. With one exception that covers many small businesses: Article 4(5) of the directive exempts microenterprises providing services, meaning those with fewer than 10 employees and a turnover or balance sheet total not exceeding 2 million euros under Recommendation 2003/361/EC. Below that threshold the obligation does not apply; the readability problem remains.
The technical reference is still WCAG. Anyone who has set their typography by eye over the last ten years almost certainly has at least one contrast problem to fix, and it is better to find it before somebody else does: in the guide on how to build an SEO-friendly website we listed the early choices that later prove expensive.
Google Fonts from Google's servers: the European problem
When you embed Google Fonts with the classic <link> to fonts.googleapis.com, the user's browser contacts a Google server and hands over its IP address. On 20 January 2022 the Regional Court of Munich, 3rd civil chamber, case 3 O 17493/20, ruled that this transfer without informed consent breaches the GDPR and ordered the site operator to pay 100 euros in damages under Article 82.
A hundred euros is a token amount. The problem is that the ruling opened the way to waves of serial claims in Germany and pushed half of Europe to move its fonts in-house. It is a German ruling under the EU GDPR and does not bind UK courts, but UK GDPR is built on the same text, and a UK site with visitors in the EU is exposed anyway. The technical fix takes half an hour: download the WOFF2 files for only the weights and subsets you use, put them on your own domain and declare them with @font-face. You also remove a connection to a third-party domain, which on mobile is often worth more than compressing the file.
Self-hosting is not an automatic legal shortcut and does not replace a proper privacy assessment, but it removes the request that started the litigation.
The only way a font can really get you penalised
There is one case where typography becomes a direct problem with Google, and it is not the choice of family: it is using text properties to hide text. Text with font-size: 0, text the same colour as the background, text positioned off-screen with the intent of having the crawler read it and people not. The hidden text and link abuse section of Google's spam policies names exactly these cases, including opacity and font size set to zero. The risk is not a lost position, it is a manual action. The same page makes clear that accordions, tooltips and text intended for screen readers do not count as a violation, because there the intent is the user experience.
It is the same family of techniques we covered in the articles on keyword stuffing, cloaking and black hat SEO. It can also happen without any ill intent: an accessible menu that hides labels with font-size: 0 instead of using screen-reader-only classes produces the same pattern.
How to set up typography without paying for it in performance
Seven decisions, in order of impact on the numbers.
- Two families at most. One for headings and one for body text, or a single family with two weights. Every extra family is one more file on the critical path.
- Three or four weights in total, at most. The browser's synthetic bold is ugly, but six real weights are 130 KB nobody asked you for.
- Only the subset you need. For an English-language site that is latin, plus latin-ext only if you use characters from Central European languages. Subsetting is what takes a file from 48 KB to 12.
- WOFF2 and nothing else. In 2025, 65% of font requests on the web were WOFF2 according to the Web Almanac. Older formats served browsers that no longer exist.
font-display: swapon every declaration. If the font arrives late, the text is visible anyway. It is the line of CSS with the best ratio of effort to result.- Preload only the truly critical files. One or two, the ones that render the heading and the first paragraph. Preloading everything means preloading nothing, as the web.dev documentation itself points out.
- Body text from 16 pixels up, with contrast checked. Not by eye: with an automated check against the 4.5:1 ratio.
For the before-and-after comparison, measure LCP with field data, not in the lab: they are two different numbers and only the first counts for Google. The order in which to tackle the other fixes is in our guide to technical SEO, and for the files that weigh more than fonts, what we wrote on image optimisation still applies.
When typography is part of a rebuild, it is worth deciding it together with the site architecture, not afterwards: that is how we work on our web development and SEO consultancy projects, and you will find some cases in the projects section.
Frequently asked questions
No. Google's John Mueller stated on 26 May 2020 that the choice of font does not matter for SEO. No family ranks better than another. What affects rankings is the file size, how the font behaves while loading and how readable the text is for the people who land on the page.
It depends on how many weights and subsets you load. The Latin subset file of a popular family weighs between 7.7 and 48 KB in WOFF2, according to the measurements we took in September 2026. The problem is not Google Fonts in itself, but loading six weights and every alphabet when you need two and one.
In the UK and the EU, yes, for two reasons. It removes a connection to a third-party domain on the critical path, and it removes the transfer of the visitor's IP address to Google that the Regional Court of Munich, on 20 January 2022, found to breach the GDPR in case 3 O 17493/20.
The practical reference for body text is 16 pixels, but the binding rule is a different one: WCAG criterion 1.4.4 requires that text can be resized up to 200% without losing content or functionality, and criterion 1.4.3 sets a minimum contrast of 4.5:1 against the background.
The family you choose cannot. Using text properties to hide text can: font-size set to zero, text the same colour as the background or moved off-screen all count as hidden text under Google's spam policies and can lead to a manual action.
One last observation that is rarely heard in the industry. When an answer is generated by a conversational assistant, your typography disappears: the text remains, without your typeface, your line spacing or your contrast. As a growing share of searches end without a click, typographic work stops being an investment in your whole audience and becomes an investment in the minority who actually reach the site. That does not make it less useful, it makes it more selective: it is worth doing well on the pages where someone buys or fills in a form, much less on the pages that only exist to be cited.
