What should I check after publishing my site?
After you publish your site to Production, the TeleportHQ Publish window shows a line that starts with After publishing:. It says either "nothing to fix on the site" or how many things visitors would run into, such as broken links, empty pages or placeholder images. Click it to see each problem with a button that takes you to where it's fixed; images without alt text and form fields without a label also link to the Accessibility check. Then click Check page loading speed to see which pages open slowly on phones.
Before you start
- Publish to Production first. The After publishing line appears once the project has been published to Production, and not while a publish is running. See How to publish your site.
- Nothing here changes your project. The list and the speed check only read your project and your last publish.
Steps
- Open your project in the editor.
- At the top right, click Publish.
- In the window's left menu, make sure Publish is selected. At the top, keep Production selected.
- Scroll down past Custom domain and the Password Protection and Installable app options, to the line After publishing:. It reads, for example, After publishing: 3 things to check, or After publishing: nothing to fix on the site.
- Click the line to open it. Each problem has a title that counts it, for example 2 links lead to a deleted page, a sentence on how to fix it, and the items it's about.
- Click the button next to an item, for example Show link or Open page. The Publish window closes and the editor shows that item.
- Fix the item. When you open Publish again, the list is still open, and the items you fixed are gone from it.
- Click Publish to Production again: your fixes go live with that publish.
What the list checks
The list puts what hurts visitors most first. Only what visitors can open is checked: your admin panel, pages you left out of the published site, the invoice and the email templates aren't.
| What you see | What it means | Button |
|---|---|---|
| Some features are not set up yet | Parts of your site don't work for visitors until they're set up. | Open the missing setup |
| N links lead to a deleted page | Visitors who click them land on your 404 page. Point each link to an existing page. | Show link |
| N forms send submissions nowhere | Nothing is saved and nobody is told when a visitor submits them. Store the submissions or send notifications. | Open form |
| N pages are empty | They publish as blank pages. Add content, or delete the pages you don't need. | Open page |
| N images have no picture | Visitors see an empty frame where a picture should be. Choose a picture in the right panel, or delete the element. | Show image |
| N images still show the placeholder | Visitors see the builder's sample picture. Choose your own in the right panel. | Show image |
| N pages have no search title or description | Search engines show them in results. Fill them in under Meta Settings in the page's settings. | Open settings |
| N pages are not linked from anywhere | Visitors reach them only by typing their address. Link them from your menu, or leave them if that's on purpose. | Open page |
| N images have no alt text | Screen readers and search engines can't tell what the image shows. Describe it in its alt text. | Show image, and Open accessibility check |
| N images have placeholder alt text | Screen readers read it aloud, search engines index it, and visitors see it when the picture doesn't load. Describe what each image shows. | Show image |
| N form fields have no label | Screen readers can't tell visitors what each field is for. Give it a placeholder or an aria-label. | Show field, and Open accessibility check |
A problem with many items shows the first 3. Click Show N more to see the rest.
Fix alt text and labels in the Accessibility check
The N images have no alt text and N form fields have no label problems end with an Open accessibility check link. Click it: the Publish window closes and the TeleportHQ Accessibility check panel opens over the editor. It checks every page and component against 11 rules, such as missing alt text, low-contrast text or a skipped heading level. Filter the results with Errors, Warnings or All.
For images and icon-only buttons and links, Suggest with AI writes an alt text or a name for one item, and Suggest for all does it for the whole group. These suggestions use AI tokens on every plan. Fix all with the AI assistant and Ask the AI assistant hand the work to the AI Assistant. Fixes are saved to your project right away and go live the next time you publish.
You can also open the panel at any time: in the Project Menu (the logo at the top left), click Accessibility check, or run Check accessibility in the command palette. See How to use the command palette.
Check page loading speed
The Page loading speed part, at the end of the open list, shows how much code each page makes the browser download on a first visit, read from your last publish. Pages over 170 kB open noticeably slower on phones.
- Open the After publishing list, as in the steps above.
- Under Page loading speed, click Check page loading speed. Reading your last publish takes a moment.
- Read the verdict at the top, for example "Every page your visitors open loads fast." or "2 pages your visitors open are slow on phones."
- Check the list below it: your 6 heaviest pages, each with its size and a label.
| Label | Size of the page's first visit |
|---|---|
| Fast | Under 170 kB |
| Slow on phones | 170 kB to 250 kB |
| Very slow on phones | 250 kB or more |
When a page is slow, the list adds tips under To make a page lighter:
- Remove the elements and components a page doesn't use, including ones hidden on some screen sizes: they're downloaded anyway.
- Split long pages: move the sections not every visitor needs to a page of their own.
- Keep only the carousels, video players and embedded widgets the page needs: each one adds its own code.
Publish again after your changes, then check again to see the difference. Your admin panel's pages are listed apart: only your team opens them, so they don't slow down your site for visitors.
Troubleshooting
"Publish the site again: the speeds are read from its latest build." TeleportHQ has no record of your last Production build. Click Publish to Production, then check again.
"The build log could not be read. Projects on your own Vercel account show it there." The speed check couldn't read your last publish. Click Try again. If you publish with your own Vercel account, look at the build in Vercel instead.
"The build log has no page list to read. Publish again to get one." Click Publish to Production, then check again.
"This item no longer exists in this project." You deleted the item after opening the list. Close the list and open it again: it reads your project again.
Good to know
- The list reads your project as it is now, not the live site. A problem you fixed disappears from the list straight away, but visitors see the fix only after your next publish.
- Broken links before you publish. The Issues chip at the top left of the editor lists every link that leads nowhere on your site: on buttons, navigation and text links of every page and component, and in Blog posts and Help Center articles. It reads your project, so it works before your first publish. See How to find and fix broken links on your site.
- For a deeper check of your search settings, see How to check your site's SEO health.