An embed puts another company's code on your page, which means their performance, availability, and data collection become part of your site. Each one should earn its place, and most sites carry several nobody chose deliberately.

What an embed actually does

It fetches code from somebody else's server and runs it in your visitor's browser, on your page.

Three consequences follow, and none is obvious from the paste-this-snippet instruction.

Their speed becomes your speed. If their server is slow, your page waits.

Their availability becomes your availability. If their service is down, your page has a hole in it or fails to finish loading.

Their data collection happens on your site. Many embeds set cookies and record visitors, which becomes something you are responsible for disclosing.

The common ones and what they cost

Maps

Frequently the single heaviest element on a contact page, loading a substantial amount of code to show a location that a static image and a link would convey.

For most small businesses a screenshot of the map, linked to the mapping service, is faster, lighter, and does the same job. The interactive version earns its place only where visitors genuinely need to explore.

Booking and scheduling widgets

Genuinely valuable and worth the weight, since they complete transactions.

The caution is that they frequently take a moment to appear, and a blank space where the booking should be looks broken. Reserving the space and showing something while it loads matters here more than elsewhere.

Review feeds

Load slowly, frequently look unstyled, and occasionally display nothing when the service is unavailable.

The alternative worth considering is quoting reviews as text on the page with a link to the source. That is faster, always renders, and is readable by search engines in a way an embedded feed is not.

Social feeds

The worst value of the common embeds. Heavy, frequently broken when the platform changes, and a live demonstration of how infrequently you post.

A stale feed showing a post from eight months ago is worse than no feed.

Video

Standard video embeds load a considerable amount of code before anybody presses play.

Using a thumbnail that loads the player only on click removes almost all of that cost while behaving identically to the visitor.

Chat widgets

Persistent, present on every page, and loading on every visit whether used or not.

The privacy dimension

The consequence most small businesses have not considered.

Many embeds set cookies or transmit information about your visitor to the provider, sometimes before any interaction. That happens on your site, which makes it something your privacy statement should account for.

Which providers, what they collect, and where it goes are questions worth being able to answer, particularly if you have clients who ask. A business that cannot list what runs on its own pages cannot answer them.

Where consent requirements apply to non-essential tracking, embeds are frequently the thing being consented to, which is a reason to know which ones are there.

Loading them properly

  1. Reserve the space so the layout does not jump when the embed appears.
  2. Defer anything below the fold until it is approached.
  3. Load on interaction where possible, such as a video thumbnail or a map that activates on click.
  4. Only on the pages that need it, rather than site-wide by default.
  5. Handle failure, so a service being down leaves a sensible message rather than an empty box.

The fourth is the one most often wrong. A booking widget and a chat script frequently load on every page including ones where they are irrelevant, because installing them globally was easier.

The audit

Worth doing once, because most sites carry embeds nobody chose.

Open the browser developer tools, load your homepage, and look at which external domains are being contacted. The list is usually longer than expected and contains things installed years ago for a purpose nobody remembers.

For each one: what is it for, is it still used, and what would break without it. Anything failing all three should be removed.

That exercise typically removes two or three requests from every page load and reduces what you are disclosing at the same time.

The judgement

An embed is worth it when it completes something a visitor came to do, such as booking or paying.

It is rarely worth it when a static alternative conveys the same information, which covers maps, review displays, and social feeds for most small business sites.

The general rule is that anything transactional earns its weight and anything decorative does not, and the accumulated weight of the decorative ones is a common cause of slow pages, as covered in what slowness actually costs you.

Frequently asked questions

What does an embed actually do?

It runs another company's code in your visitor's browser on your page, so their speed, their availability, and their data collection all become part of your site.

Which embeds are usually not worth it?

Maps where a static image and a link would do, review feeds, and social feeds, which are heavy and frequently demonstrate how rarely you post.

Which are worth the weight?

Anything transactional, such as booking or payment, since it completes something the visitor came to do.

How should video be embedded?

With a thumbnail that loads the player only on click, which removes almost all the cost while behaving identically to the visitor.

What is the privacy consequence?

Many embeds set cookies or send visitor information to the provider before any interaction, on your site, which your privacy statement should account for.

How do I audit what is running?

Open developer tools, load your homepage, and look at which external domains are contacted. The list is usually longer than expected and contains forgotten installations.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Contact page waiting on a map nobody explores?

We audit what is actually running on your pages, which usually removes several requests and shortens what you have to disclose.

Start a Conversation