{"json_modified": "2015-12-30T15:48:48.619408", "slug": "Web/HTML/Optimizing_your_pages_for_speculative_parsing", "tags": ["Avanzado", "HTML", "HTML5", "Desarrollo web"], "locale": "es", "title": "Optimizar sus p\u00e1ginas para an\u00e1lisis especulativo", "translations": [{"title": "Optimizing your pages for speculative parsing", "url": "/en-US/docs/Web/HTML/Optimizing_your_pages_for_speculative_parsing", "tags": ["NeedsUpdate", "Advanced", "HTML", "HTML5", "Web Development"], "summary": "Traditionally in browsers the HTML\u00a0parser 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.", "localization_tags": [], "locale": "en-US", "last_edit": "2015-01-14T18:42:22", "review_tags": []}, {"title": "Optimizing your pages for speculative parsing", "url": "/pt-BR/docs/Web/HTML/Optimizing_your_pages_for_speculative_parsing", "tags": [], "summary": "Traditionally in browsers the HTML\u00a0parser 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.", "localization_tags": [], "locale": "pt-BR", "last_edit": "2014-06-24T05:49:18", "review_tags": []}, {"title": "Optimizing your pages for speculative parsing", "url": "/ru/docs/Web/HTML/Optimizing_Your_Pages_for_Speculative_Parsing", "tags": [], "summary": "Traditionally in browsers the HTML\u00a0parser 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.", "localization_tags": [], "locale": "ru", "last_edit": "2014-07-02T22:52:58", "review_tags": []}, {"title": "Optimizing your pages for speculative parsing", "url": "/fr/docs/Web/HTML/Optimizing_your_pages_for_speculative_parsing", "tags": [], "summary": "Traditionally in browsers the HTML\u00a0parser 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.", "localization_tags": ["inprogress"], "locale": "fr", "last_edit": "2014-09-27T02:02:13", "review_tags": []}, {"title": "\u6807\u9898", "url": "/zh-CN/docs/Web/HTML/Optimizing_your_pages_for_speculative_parsing", "tags": [], "summary": "Traditionally in browsers the HTML\u00a0parser 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.", "localization_tags": ["inprogress"], "locale": "zh-CN", "last_edit": "2015-10-08T19:20:21", "review_tags": []}], "modified": "2015-12-30T15:48:47", "label": "Optimizar sus p\u00e1ginas para an\u00e1lisis especulativo", "localization_tags": ["inprogress"], "url": "/es/docs/Web/HTML/Optimizing_your_pages_for_speculative_parsing", "last_edit": "2015-12-30T15:48:47", "summary": "Tradicionalmente en los navegadores el analizador de HTML corre en el hilo de ejecuci\u00f3n principal y se queda bloqueado despu\u00e9s de una etiqueta </script> hasta que el c\u00f3digo se haya recuperado y ejecutado. El analizador de HTML de Firefox 4 y posteriores soporta an\u00e1lisis especulativo fuera del hilo de ejecuci\u00f3n principal. Este\u00a0analiza anticipadamente mientras el codigo est\u00e1 siendo\u00a0descargado y ejecutado. Como en Firefox 3.5 y 3.6, el analizador de HTML es el que inicia la carga especulativa de c\u00f3digo, las hojas de estilos y las imagenes que va encontrando en el flujo de la p\u00e1gina. Sinembargo en Firefox 4 y posteriores el analizador de HTML tambi\u00e9n ejecuta el algoritmo especulativo de la contrucci\u00f3n del \u00e1rbol HTML. La ventaja es que cuando lo especulado tiene exito, no hay necesidad de reanalizar la parte del archivo de entrada que ya fue analizada junto la descarga de\u00a0c\u00f3digo, \u00a0hojas de estilo y las im\u00e1genes. La desventaja es que se ha realizado un trabajo in\u00fatil cuando la especulaci\u00f3n fracasa.", "sections": [{"id": "Haciendo_cargas_especulativas_exitosas", "title": "Haciendo cargas especulativas exitosas"}, {"id": "Evitando_perder_la_salida_del_generador_de_arbol", "title": "Evitando perder la salida del generador de arbol"}], "id": 114007, "review_tags": []}