Skip to content

JavaScript rendering check

Is your page's text in the HTML the server sends, or do scripts write it after loading?

  • Checks your page
  • 3 browsers
  • 1 rule
  • Last updated

Renders the page in:ChromiumFirefoxWebKit

Free, no sign-up.

What we keep

We keep the address exactly as you send it, including anything after a “?”, and its report shows it. Anyone who has the report’s link can open it, so leave out tokens, keys and personal data.

The result appears here

Enter your page’s address and press “Check the page”. This is what the tool runs on it:

  • The page's content is written by scriptsnot started

What it checks

  • The Arabic text on the page as Chromium and Firefox draw it, and WebKit where it runs: the first 200 visible elements with Arabic text, in the page's order.
  • The Arabic words of that text that are not in the text of the HTML the scan received, before JavaScript runs, whatever their marks or tatweel. All the text of the body is there, hidden text and <noscript> and <template> included, since it is in the HTML as sent.
  • The page fails when more than half of those words are not in the HTML, in one browser at least, and the browser drew at least 20 Arabic words. With fewer, a language switch or a cookie notice that a script adds would say nothing of how the page is written.

Example

WrongHTML
<main id="app">
  <h1>قهوة عربية بالهيل</h1>
</main>
<script src="/app.js"></script>
RightHTML
<h1>قهوة عربية بالهيل</h1>
<p>قهوة عربية محمّصة تحميصاً خفيفاً ومطحونة مع الهيل، في علب تُشحن خلال يومين.</p>

How to fix

Send the page's text in the HTML from the server, and let scripts add only what interaction needs, so the text arrives before them:

  • Server-side rendering (SSR): the server builds the page's whole HTML for each request, and JavaScript takes it over in the browser. Common frameworks support it, such as Next.js, Nuxt, SvelteKit and Astro.
  • Pre-rendering (static generation): each page's HTML is built once, when the site is published, which suits pages whose content is the same for every visitor.
  • Then open "View page source" in the browser and make sure the text is there, or check the page again.
HTML
<main id="app">
  <h1>قهوة عربية بالهيل</h1>
  <p>قهوة عربية محمّصة تحميصاً خفيفاً ومطحونة مع الهيل، في علب تُشحن خلال يومين.</p>
</main>
<script src="/app.js" defer></script>

FAQ

It does. Google processes JavaScript pages in three phases: crawling, rendering, then indexing. But a page waits for rendering in a queue where it may stay a few seconds or longer, and Google says server-side rendering or pre-rendering is still a great idea, since it makes the site faster, and not all bots can run JavaScript.

Not necessarily. When the server builds the page's HTML and JavaScript then takes it over in the browser, the text is in the HTML and the page passes, even if scripts draw it again. It fails when the HTML arrives nearly empty and JavaScript writes all the text.

The check measures which words the HTML it received lacks, and not who wrote them. The scan asks for the HTML without saying which language it prefers, while the browsers ask for Arabic: a site that picks the language of its HTML on the server from that header may send the scan another language than it sends a browser. And text that a script adds beside the page's own, such as a cookie notice, counts among the words the HTML lacks.

Because it reads the Arabic text the browsers measure on the page, which is what Arablyzer is built for. Text in other languages is not counted, nor are images.

Because it renders the page in browsers and runs its scripts before it measures its text, instead of reading the HTML alone.

How we measure

Last updated Methodology and scoring

We fetch the page as ArablyzerBot, with no language preference, and read the text of its HTML as the server sends it, before JavaScript runs. We then render it in Chromium and Firefox, and WebKit on servers with an isolated network, with every request it makes going through a proxy that refuses private addresses. In each browser we read the first 200 visible elements with Arabic text and the first 200 characters of each element's text, and count their Arabic words, each run of Arabic letters, read as one word whatever its marks or tatweel. We gather the words of all the text in the body of that HTML, hidden text and <noscript> and <template> included, and not the text of scripts and styles. A browser is judged only when it drew at least 20 Arabic words, a number of our own for this check. The page fails when more than half of those words in a browser are not in the HTML's text, and we name the browsers where this holds. The same page gives the same result every time.