aboutsummaryrefslogtreecommitdiff
path: root/files/pt-br/glossary/speculative_parsing/index.html
diff options
context:
space:
mode:
Diffstat (limited to 'files/pt-br/glossary/speculative_parsing/index.html')
-rw-r--r--files/pt-br/glossary/speculative_parsing/index.html3
1 files changed, 2 insertions, 1 deletions
diff --git a/files/pt-br/glossary/speculative_parsing/index.html b/files/pt-br/glossary/speculative_parsing/index.html
index 5da1c3efa2..3a6c4495ff 100644
--- a/files/pt-br/glossary/speculative_parsing/index.html
+++ b/files/pt-br/glossary/speculative_parsing/index.html
@@ -1,7 +1,8 @@
---
title: Optimizing your pages for speculative parsing
-slug: Web/HTML/Optimizing_your_pages_for_speculative_parsing
+slug: Glossary/speculative_parsing
translation_of: Glossary/speculative_parsing
+original_slug: Web/HTML/Optimizing_your_pages_for_speculative_parsing
---
<p>Traditionally in browsers the HTML parser has run on the main thread and has blocked after a <code>&lt;/script&gt;</code> tag until the script has been retrieved from the network and executed. The HTML parser in Firefox 4 and later supports speculative parsing off the main thread. It parses ahead while scripts are being downloaded and executed. As in Firefox 3.5 and 3.6, the HTML parser starts speculative loads for scripts, style sheets and images it finds ahead in the stream. However, in Firefox 4 and later the HTML parser also runs the HTML tree construction algorithm speculatively. The upside is that when a speculation succeeds, there's no need to reparse the part of the incoming file that was already scanned for scripts, style sheets and images. The downside is that there's more work lost when the speculation fails.</p>
<p>This document helps you avoid the kind of things that make speculation fail and slow down the loading of your page.</p>