# Fast pages

> Published pages are static HTML with almost no JavaScript, no font downloads and images sized to each screen, so they load quickly on phones.

URL: https://office.greatwork.company/site/features/page-speed
Last updated: 2026-11-21

Published pages are static files with almost no JavaScript, no font downloads and images sized to each screen.

## Static pages by default

When you publish, every page is rendered once into a plain HTML file. A visitor's phone downloads that file and your images, not a page-building app. The only scripts are the ones a page actually needs: the phone menu, form checks and one small analytics beacon.

## No font downloads, smaller images

Theme fonts come from type already on your visitors' devices, so text shows up right away instead of waiting on a font file. Images are WebP at the size each screen needs, loaded as people scroll, with sizes set so nothing jumps around.

## Why it matters for a small business

People looking for a plumber or a dinner spot are usually on a phone, often on a weak connection, and they leave slow pages. Google also measures loading speed and layout stability on real phones (Core Web Vitals) as part of how it judges a page.

## Example: What a phone downloads for a plumber's home page

Brightline's home page is one HTML file, a stylesheet, a small script for the menu and form, and five images in WebP. No font files, no chat widget until you turn one on, no tracking scripts unless Luis adds them and a visitor accepts.

## How to set it up

1. Nothing to set up: every published page is static.
2. Add alt text and use the media library so images get resized.
3. Add third-party scripts only if you need them; each one adds weight.

## Questions

### Do embeds slow my site down?

An embed loads the other service's page, so it adds weight. Built-in video and map sections use privacy-friendly players and maps that don't set cookies.

---

Office by Great Work. Questions or corrections: hello@greatwork.company
