How Insites handles frames and iframes

Insites considers both frames and iframes to be separate pages. Frames are only counted if the frame has a URL and that exists within the allowed URLs for the website.

Frames and iframes count towards the cookies and speed of the parent page. So if a webpage relies on a slow iframe, for example, the Speed test will detect that. The Cookie law test will detect cookies set by frames.

This means:

  • Most common iframes – such as Facebook plugins – will not have their content tested, as their URL is outside of the current website.
  • Websites which use frames for content will be tested but those frames will count as separate pages.
  • The use of 3rd party iframes can impact your speed and cookie usage.

Example

Consider a website with two files:

index.html

<html>
<body>
<h1>This is a demo</h1>
<iframe src="iframe.html"></iframe>
</body>
</html>

iframe.html

<html>
<body>
<h1>This is an iframe</h1>
</body>
</html>

Insites will download the first page (index.html) and consider it linking to the second page (iframe.html). Both pages will be fully tested, but they will count as two separate pages. The speed results for index.html will include the time taken to load iframe.html.

See also