Elementor is a page builder plugin that lets you design WordPress pages without writing code, using drag and drop while seeing changes immediately. The essence of how to use Elementor comes down to four steps: first define global colors and fonts in Site Settings, build the page with containers, check every section separately in tablet and mobile modes, and finally enable Elementor’s own performance settings.

This guide was prepared for beginners; every setting and menu name described is based on documentation in Elementor’s official help center. Menu names may vary slightly by version, but the underlying logic is the same.

What is Elementor, and how does it work?

Elementor is a visual editor running within WordPress: elements (widgets) from the left panel are dragged onto the page, their settings are changed through the panel, and the result is visible on the same screen. The free version of the plugin provides basic layout and content elements; Elementor Pro adds extra tools such as a theme builder, forms, and popups. Which version is sufficient depends on the website’s needs.

Two generations of editors coexist in Elementor. In the long-established 3.x editor, each element has Content, Style, and Advanced tabs. According to Elementor’s help documentation, the V4 editor manages styles through classes, uses two tabs for each element, General and Style, and has V4 elements enabled by default in Elementor 4.x releases. V4 elements fit inside existing 3.x containers and work alongside older pages.

A page builder is not mandatory for every website. WordPress’s own block editor may be enough for simple pages; for visually distinctive corporate and campaign pages containing many different section layouts, a tool such as Elementor speeds up editing. The general framework for the platform decision is addressed in the WordPress or a website builder comparison.

Before you begin: installation and initial settings

Organizing the plugin’s and website’s basic settings before starting page design with Elementor prevents the need for page-by-page corrections later. Elementor is installed through the Plugins section in the WordPress dashboard; choosing a lightweight theme compatible with Elementor reduces conflicts with the theme’s own styles.

The server must also meet the plugin’s requirements. According to Elementor’s system requirements page, the plugin works on WordPress 6.5 and above with a minimum of PHP 7.4, although PHP 8.x is recommended; a WordPress memory limit of at least 256 MB is required, with 512 MB recommended. If the editor panel does not load or errors occur while saving, this memory limit is often the first place to look.

The Settings screen under the Elementor menu in the WordPress dashboard lets you determine which content types will use Elementor and choose whether default colors and fonts are managed by the theme or Elementor. The option on the same screen allowing unfiltered file uploads, such as SVG and JSON, should be enabled only when truly necessary because, according to Elementor’s own warning, it poses a security risk.

Understanding containers: what replaced sections and columns?

In Elementor, pages are now built with containers instead of sections, columns, and inner sections. According to Elementor’s container documentation , flexbox-based containers allow the width, height, and order of their elements to adapt to the available space; they offer better page loading and more responsive controls. The container is the default layout element on new Elementor websites.

A container arranges its elements horizontally (row) or vertically (column); this direction can be set separately for each device size. Three cards placed side by side on desktop are stacked on mobile by changing the same container’s direction. There is also a separate grid container for regular grids consisting of rows and columns.

Pages built with older sections and columns can be converted using the “Convert to container” option. Elementor states that this is a one-way process and that a page converted to containers cannot be returned to the section-and-column structure; the page should be backed up before conversion.

Building your first page with containers step by step

When a new page is built as blocks, each serving a single purpose, both editing and mobile adaptation become easier. For a simple service page, the workflow is as follows:

  1. Create a new page in WordPress and press the “Edit with Elementor” button.
  2. Add a container using the plus icon on the canvas; each main section of the page, such as introduction, services, process, and contact, becomes a separate top-level container.
  3. Add heading, short text, and button elements to the introductory section; choose the heading element’s HTML tag so that H1 is used once on the page.
  4. Create a container for service cards, set its direction to row, and use an inner container for each card.
  5. Set spacing and alignment through the container’s gap and alignment settings rather than on individual elements.
  6. Save sections that will be reused, such as a contact call to action, as templates.
  7. Publish the page after checking it in tablet and mobile modes.

Using more nested containers than necessary needlessly enlarges the page’s HTML structure. Elementor’s container and performance documentation demonstrates with an example that building the same design with fewer containers reduces the page’s load.

Page contents

Trustworthy web agency: handshaking client and team, trust shield illustration

Global colors and fonts: Site Settings

Colors and fonts are not chosen individually for every element; they are defined once in Site Settings, and these global values are used on all pages. Site Settings can be accessed through the Elementor icon in the editor’s top bar or the Elementor menu in the WordPress dashboard.

The Design System section includes predefined global colors and global fonts for primary, secondary, text, and accent styles; new brand-specific colors and text styles can also be added. The Theme Style section brings together default appearances for headings, buttons, images, and form fields, while the Settings section contains site-wide options such as site identity, layout, lightbox, and custom CSS.

The main benefit of using global values becomes apparent when changes are made. When the brand color is updated, every button and heading linked to that global color is refreshed in one action; elements with manually entered color codes must instead be found and corrected individually. Elementor’s help documentation also states that colors and fonts varying between pages can confuse visitors and weaken brand identity.

Let’s review your Elementor pages together

A free preliminary assessment examines together whether the existing Elementor website uses global styles, how simple its container structure is, and where its mobile appearance breaks. The points requiring correction are noted in order of importance.

Responsive design: desktop, tablet, and mobile modes

In Elementor, every page can be adjusted separately for desktop, tablet, and mobile; switching is done through the device icons in the editor’s top bar. According to Elementor’s mobile editing documentation , the default breakpoints are as follows:

Device modeDefault screen widthWhat to check
DesktopWider than 1024 pixelsOverall layout, image proportions, menu
TabletBetween 767 and 1024 pixelsCard row/column arrangement, spacing
MobileNarrower than 767 pixelsHeading size, button width, form fields, horizontal overflow

Settings are inherited from larger screens to smaller ones: a font size set on desktop also applies on tablet unless changed there; a value set on tablet is also passed to mobile. According to the documentation, widescreen mode is the exception to this rule and does not affect the other screens. Additional sizes, such as widescreen, laptop, tablet extra, and mobile extra, can also be defined using the Additional Custom Breakpoints feature.

Instead of hiding an element on mobile and placing a mobile-specific copy in its place, a cleaner method is to change the container direction and element order by device. Elementor states that custom ordering can be set for each breakpoint in containers, eliminating the need for additional sections hidden according to device.

Templates, the Structure panel, and history

Three tools speed up work in Elementor: reusable templates, the Structure panel showing a tree view of the page, and the History panel allowing changes to be undone. Templates allow blocks such as a contact section, client reference strip, or call-to-action box to be designed once and added to different pages.

On long, layered pages, finding an element by clicking it on the canvas becomes difficult. The Structure panel (Ctrl/Cmd + I) lists all elements on the page as a tree; elements behind others or hidden can also be reached here, and elements can be reordered by dragging.

The History panel has two tabs. The Actions tab keeps every step performed during that editing session; the Revisions tab lists versions created each time the page is saved or published and allows you to return to the selected version. Ctrl/Cmd + Z undoes the last step.

Transparent pricing: calculator and budget planning illustration

Elementor’s own performance settings

Elementor offers a series of options in the Performance and Features tabs of its settings screen to improve page speed. The main settings listed in Elementor’s performance features documentation are as follows:

  • Optimized Image Loading: gives the page’s largest image high loading priority and lazy-loads images below the fold.
  • Lazy Load Background Images: loads background images other than the first as they approach the screen.
  • Optimized Gutenberg Loading: removes unused block editor scripts and styles from the page.
  • Inline Font Icons: outputs icons as inline SVG without loading separate icon libraries.
  • Load Google Fonts Locally: serves fonts from the website’s own server instead of Google’s servers; it has been disabled by default since Elementor 3.32.1 and must be enabled manually.
  • Element Caching: stores and reuses element output; it is an experimental feature and should not be used on dynamic elements displaying visitor-specific content.

According to the help center, simplified HTML output (optimized DOM), previously optional, has been permanently integrated into the core since version 3.19. Backups should be taken before changing these settings, and pages should be checked on different devices after each change.

Configuration mistakes that slow down Elementor pages

Slow Elementor websites usually result from how the page is built rather than from the plugin itself. Unnecessarily nested containers, large sliders that autoplay on opening, different animations in every section, and numerous font weights increase the page’s load.

Large images uploaded without compression and numerous plugin packages providing extra Elementor elements have the same effect. The asset loading documentation also notes that third-party plugins that fail to implement their own loading improvements correctly can cause conflicts. Measurement and improvement steps are explained in the Core Web Vitals guide ; when comprehensive work is needed, WordPress speed optimization is handled as a separate task.

SEO and accessibility fundamentals with Elementor

A page created with Elementor being understandable to search engines and all users depends on proper heading structure and meaningful content. A heading element’s visible size and HTML tag are independent of each other; therefore, every page should have a single H1, and subheadings should follow the H2 and H3 hierarchy. Choosing H1 or H2 solely for visual size disrupts the page’s structure.

Image alternative text should be filled in through the media library, and button and link text should explain where they lead. If color contrast between text and background is checked when choosing global colors, page-by-page corrections will not be necessary later. Together, these basic rules also form the core of the SEO-friendly web design approach.

Common beginner mistakes and the correct approach

Most problems seen on first Elementor pages arise from the same habits and are easily prevented by establishing the right structure from the outset. The most frequently encountered mistakes and their corresponding solutions are as follows:

  • Manually setting colors and fonts on every element: without global values, dozens of elements must be corrected individually when the brand color changes. The correct approach is to choose colors and text styles only through Site Settings.
  • Leaving mobile appearance until the end: a page completed on desktop encounters overflowing headings and horizontal scrolling problems on mobile. Tablet and mobile modes should be checked immediately after each section is completed.
  • Creating spacing with empty elements: empty spacers added to create gaps bloat the page; spacing is set through the container’s padding and gap settings.
  • Choosing heading tags according to appearance: assigning H1 to every heading just to make it look large disrupts the page structure; size is determined through styling, while the tag is determined by the content hierarchy.
  • Installing a new element package for every need: additional plugins installed for a single element increase load and update monitoring; a solution should first be sought using Elementor’s own elements.
  • Experimenting on the live website: major design changes and experimental features are tried after taking a backup first, preferably on a test copy.

Let’s plan your Elementor project together

After a few pages, the question of how to use Elementor gives way to “how can this website remain maintainable?” If a new website is to be built or existing Elementor pages simplified, the global style structure and page templates can be determined together from the beginning. In the WordPress website development process, dashboard training is also provided with delivery; you can write through WhatsApp or call for a free preliminary assessment.

Frequently asked questions

First define global colors and fonts in Site Settings, then build the page with containers and add elements by dragging them from the left panel. Check every section separately in tablet and mobile modes, and finally review the performance settings.

Elementor has a free version that provides basic layout and content elements. Additional tools such as a theme builder, forms, and popups come with Elementor Pro; which is needed depends on the website’s requirements.

A container is a flexbox-based layout element that replaces the old section-and-column structure. It arranges its elements horizontally or vertically, and this direction can be set separately for each device size.

Select the mobile icon in the editor’s top bar and change element settings in this mode. Because settings are inherited from larger screens to smaller ones, only values that need to differ on mobile are edited.

Most slowness comes from how the page is built; unnecessary nested containers, large images, heavy animations, and numerous additional plugins increase load. Elementor’s performance settings, such as optimized image loading and local fonts, should also be enabled.

Open Site Settings through the Elementor icon in the editor’s top bar and edit global colors under Design System. All elements linked to the global color update automatically when saved.

Yes, pages built with sections and columns can be converted using Convert to Container. According to Elementor, the process is one-way, so a backup should be taken before conversion.