Before you launch: performance, accessibility and upkeep

The editor's device preview is a good guide, but it isn't a phone. Before launch, open every key page on a real phone and check:

• No horizontal scrolling. The usual cause is an element with a fixed width or a large negative margin.
• Headlines fit without awkward one-word lines.
• Buttons are big enough to tap, about 44 px high or more.
• The menu toggle opens, closes and scrolls if it's long.

• Images: sensible dimensions, modern formats (WebP/AVIF), lazy loading below the fold. Elementor One credits can optimize them in bulk, or use any good image plugin.
• Fonts: two families at most, only the weights you use, loaded locally (an option in Elementor's Performance settings).
• Plugins: deactivate and delete anything you don't use, especially leftover addon packs.
• Caching: turn on your host's page cache or a caching plugin. After big design changes, clear Elementor's generated files from the admin bar's clear-cache option.
• Measure: run PageSpeed Insights on the home page and a typical post, and fix the biggest item first.

• Press Tab through the page: you can reach every link and button, and you can always see which one has focus.
• Headings follow the h1 → h2 → h3 order (lesson 05).
• Every meaningful image has alt text. Decorative images have empty alt text.
• Text contrast is readable. Light grey on white is the classic failure.
• Popups can be closed with Esc, and focus doesn't get trapped behind them.

Elementor One includes accessibility scans and AI-assisted fixes if you want automation. The checks above catch most problems for free.

• Install one SEO plugin and set a title and meta description for key pages.
• Set Settings › Reading so search engines are allowed. Staging sites often have this switched off, and it gets copied to live.
• Add privacy and cookie pages, plus a consent banner if you use analytics or marketing tags. Elementor One includes a cookie consent tool, or use a dedicated service.
• Make sure transactional email (forms, WooCommerce) is sent through SMTP or an email service, not plain PHP mail.

• Backups daily, stored off the server. Test a restore once.
• Updates monthly: back up, update on staging, check the key pages, then update live. Read Elementor's changelog for major versions.
• Design system first. When something needs to change site-wide, change the Variable, Class or Component, not individual pages.

You now know the whole Elementor workflow: layout, styling, design system, reuse, templates, popups and launch. The fastest way to get fluent is to build one real site end to end.

If you'd like a head start, the Katka template pack gives you 135 page templates and 52 popups to take apart, restyle with your own Classes and make your own. Thanks for learning with me. — Barna