Translations < Spanish (Spain) < Stable Readme (latest release) < GlotPress

New to Translating WordPress? Read through our Translator Handbook to get started. Hide

Translation of Stable Readme (latest release): Spanish (Spain)

← 1 2 3 … 6 →

Prio	Original string	Translation	—
↑	Enables browsers to speculatively prerender or prefetch pages to achieve near-instant loads based on user interaction. Priority: high	Permite a los navegadores hacer precarga o prelectura de páginas para conseguir cargas prácticamente instantáneas en base a la interacción del usuario.	Details
Original current Permalink to translation Translation History View original in consistency tool Discussion Enables browsers to speculatively prerender or prefetch pages to achieve near-instant loads based on user interaction. Comment Short description. Permite a los navegadores hacer precarga o prelectura de páginas para conseguir cargas prácticamente instantáneas en base a la interacción del usuario. You have to log in to edit this translation. Meta Discussion Others Status: current Added: 2025-02-06 09:59:03 UTC Translated by: Fernando Tellado (fernandot) Priority of the original: high Translation Memory Other locales History
↑	Speculative Loading Priority: high	Speculative Loading	Details
Original current Permalink to translation Translation History View original in consistency tool Discussion Speculative Loading Comment Plugin name. Speculative Loading You have to log in to edit this translation. Meta Discussion Others Status: current Added: 2024-06-21 07:10:23 UTC Translated by: Fernando Tellado (fernandot) Priority of the original: high Translation Memory Other locales History
	Use the controls in the <strong>Speculative Loading</strong> section to configure speculative loading.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion Use the controls in the <strong>Speculative Loading</strong> section to configure speculative loading. Comment Found in installation list item. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	Visit the <strong>Settings > Reading</strong> admin screen.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion Visit the <strong>Settings > Reading</strong> admin screen. Comment Found in installation list item. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	After activation	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion After activation Comment Found in installation header. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	By default, speculative loading is only enabled for logged-out users, since unauthenticated pages are typically only eligible for caching and so more efficient to prefetch/prerender. This means that sites with frequent logged-in users on the frontend—such as e-commerce, forums, or membership sites—will not benefit from the feature. If your server can handle the additional load (for example, with persistent object caching), you can opt in to enable speculative loading for all logged-in users or for administrators only. This setting exclusively affects frontend pages; admin screens are always excluded.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion By default, speculative loading is only enabled for logged-out users, since unauthenticated pages are typically only eligible for caching and so more efficient to prefetch/prerender. This means that sites with frequent logged-in users on the frontend—such as e-commerce, forums, or membership sites—will not benefit from the feature. If your server can handle the additional load (for example, with persistent object caching), you can opt in to enable speculative loading for all logged-in users or for administrators only. This setting exclusively affects frontend pages; admin screens are always excluded. By default, speculative loading is only enabled for logged-out users, since unauthenticated pages are typically only eligible for caching and so more efficient to prefetch/prerender. This means that sites with frequent logged-in users on the frontend—such as e-commerce, forums, or membership sites—will not benefit from the feature. If your server can handle the additional load (for example, with persistent object caching), you can opt in to enable speculative loading for all logged-in users or for administrators only. This setting exclusively affects frontend pages; admin screens are always excluded. Comment Found in description paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	This plugin adds support for the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API">Speculation Rules API</a>, which allows defining rules by which certain URLs are dynamically prefetched or prerendered. This core Speculative Loading functionality was <a href="https://make.wordpress.org/core/2025/03/06/speculative-loading-in-6-8/">merged into WordPress 6.8</a>, but it only prefetches with conservative eagerness by default. In contrast, this plugin defaults to prerendering with moderate eagerness (i.e. when interacting with a link), and it provides a user interface to customize the mode and eagerness via the "Speculative Loading" section on the <em>Settings > Reading</em> admin screen.	You have to log in to add a translation.	Details
Original untranslated Permalink to original Translation History View original in consistency tool Discussion This plugin adds support for the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API">Speculation Rules API</a>, which allows defining rules by which certain URLs are dynamically prefetched or prerendered. This core Speculative Loading functionality was <a href="https://make.wordpress.org/core/2025/03/06/speculative-loading-in-6-8/">merged into WordPress 6.8</a>, but it only prefetches with conservative eagerness by default. In contrast, this plugin defaults to prerendering with moderate eagerness (i.e. when interacting with a link), and it provides a user interface to customize the mode and eagerness via the "Speculative Loading" section on the <em>Settings > Reading</em> admin screen. This plugin adds support for the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API">Speculation Rules API</a>, which allows defining rules by which certain URLs are dynamically prefetched or prerendered. This core Speculative Loading functionality was <a href="https://make.wordpress.org/core/2025/03/06/speculative-loading-in-6-8/">merged into WordPress 6.8</a>, but it only prefetches with conservative eagerness by default. In contrast, this plugin defaults to prerendering with moderate eagerness (i.e. when interacting with a link), and it provides a user interface to customize the mode and eagerness via the "Speculative Loading" section on the <em>Settings > Reading</em> admin screen. Comment Found in description paragraph. You have to log in to edit this translation. Meta Discussion Others Status: untranslated Priority of the original: normal Translation Memory Other locales History
	If you are running this plugin on a site without pretty permalinks and are confident that there are no custom query parameters in use that can cause state changes, you can opt in to enabling speculative loading via the <code>plsr_enabled_without_pretty_permalinks</code> filter:	Si estás utilizando este plugin en un sitio sin enlaces permanentes bonitos y estás seguro de que no hay parámetros de consulta personalizados en uso que puedan causar cambios de estado, puedes optar por activar la carga especulativa a través del filtro <code>plsr_enabled_without_pretty_permalinks</code>:	Details
Original current Permalink to translation Translation History View original in consistency tool Discussion If you are running this plugin on a site without pretty permalinks and are confident that there are no custom query parameters in use that can cause state changes, you can opt in to enabling speculative loading via the <code>plsr_enabled_without_pretty_permalinks</code> filter: Comment Found in faq paragraph. Si estás utilizando este plugin en un sitio sin enlaces permanentes bonitos y estás seguro de que no hay parámetros de consulta personalizados en uso que puedan causar cambios de estado, puedes optar por activar la carga especulativa a través del filtro <code>plsr_enabled_without_pretty_permalinks</code>: You have to log in to edit this translation. Meta Discussion Others Status: current Added: 2025-02-06 09:35:53 UTC Translated by: Fernando Tellado (fernandot) Priority of the original: normal Translation Memory Other locales History
	For safety reasons, the entire speculative loading feature is disabled by default for logged-in users and for sites that do not use pretty permalinks. The latter is the case because plugins often use URLs with custom query parameters to let users perform actions, and such URLs should not be speculatively loaded. For sites without pretty permalinks, it is impossible or at least extremely complex to differentiate between which query parameters are Core defaults and which query parameters are custom.	Por razones de seguridad, toda la característica de carga especulativa está desactivada por defecto para los usuarios conectados y para los sitios que no utilizan enlaces permanentes bonitos. Esto último se debe a que los plugins suelen utilizar URL con parámetros de consulta personalizados para permitir a los usuarios realizar acciones, y dichas URL no deberían cargarse de forma especulativa. Para los sitios sin enlaces permanentes bonitos, es imposible o al menos extremadamente complejo diferenciar entre qué parámetros de consulta son los predeterminados del núcleo y qué parámetros de consulta son personalizados.	Details
Original current Permalink to translation Translation History View original in consistency tool Discussion For safety reasons, the entire speculative loading feature is disabled by default for logged-in users and for sites that do not use pretty permalinks. The latter is the case because plugins often use URLs with custom query parameters to let users perform actions, and such URLs should not be speculatively loaded. For sites without pretty permalinks, it is impossible or at least extremely complex to differentiate between which query parameters are Core defaults and which query parameters are custom. For safety reasons, the entire speculative loading feature is disabled by default for logged-in users and for sites that do not use pretty permalinks. The latter is the case because plugins often use URLs with custom query parameters to let users perform actions, and such URLs should not be speculatively loaded. For sites without pretty permalinks, it is impossible or at least extremely complex to differentiate between which query parameters are Core defaults and which query parameters are custom. Comment Found in faq paragraph. Por razones de seguridad, toda la característica de carga especulativa está desactivada por defecto para los usuarios conectados y para los sitios que no utilizan enlaces permanentes bonitos. Esto último se debe a que los plugins suelen utilizar URL con parámetros de consulta personalizados para permitir a los usuarios realizar acciones, y dichas URL no deberían cargarse de forma especulativa. Para los sitios sin enlaces permanentes bonitos, es imposible o al menos extremadamente complejo diferenciar entre qué parámetros de consulta son los predeterminados del núcleo y qué parámetros de consulta son personalizados. You have to log in to edit this translation. Meta Discussion Others Status: current Added: 2025-02-06 09:36:34 UTC Translated by: Fernando Tellado (fernandot) Priority of the original: normal Translation Memory Other locales History
	Are there any special considerations for speculative loading behavior?	¿Existen consideraciones especiales para el comportamiento de carga especulativa?	Details
Original current Permalink to translation Translation History View original in consistency tool Discussion Are there any special considerations for speculative loading behavior? Comment Found in faq header. ¿Existen consideraciones especiales para el comportamiento de carga especulativa? You have to log in to edit this translation. Meta Discussion Others Status: current Added: 2025-02-06 09:36:44 UTC Translated by: Fernando Tellado (fernandot) Priority of the original: normal Translation Memory Other locales History
	A prerendered page is linked to the page that prerenders it, so personalisation may already be known by this point and changes (e.g. browsing other products, or logging in/out) often require a new page load, and hence a new prerender, which will then take these into account. But it definitely is something to be aware of and test! Prerendered pages can be canceled by removing the speculation rules <code><script></code> element from the page using standard JavaScript DOM APIs should this be needed when state changes without a new page load.	Una página en precarga está vinculada a la página que la precarga, por lo que es posible que la personalización ya se conozca en este punto y que los cambios (por ejemplo, navegar por otros productos o iniciar o cerrar sesión) requieran a menudo una nueva carga de la página y, por tanto, una nueva precarga, que los tendrá en cuenta. Pero sin duda es algo que hay que tener en cuenta y probar. Las páginas en precarga pueden cancelarse eliminando el elemento <code><script></code> de las reglas de especulación de la página mediante las API de DOM de JavaScript estándar en caso de que sea necesario cuando cambie el estado sin que se cargue una nueva página.	Details
Original current Permalink to translation Translation History View original in consistency tool Discussion A prerendered page is linked to the page that prerenders it, so personalisation may already be known by this point and changes (e.g. browsing other products, or logging in/out) often require a new page load, and hence a new prerender, which will then take these into account. But it definitely is something to be aware of and test! Prerendered pages can be canceled by removing the speculation rules <code><script></code> element from the page using standard JavaScript DOM APIs should this be needed when state changes without a new page load. A prerendered page is linked to the page that prerenders it, so personalisation may already be known by this point and changes (e.g. browsing other products, or logging in/out) often require a new page load, and hence a new prerender, which will then take these into account. But it definitely is something to be aware of and test! Prerendered pages can be canceled by removing the speculation rules <code><script></code> element from the page using standard JavaScript DOM APIs should this be needed when state changes without a new page load. Comment Found in faq paragraph. Una página en precarga está vinculada a la página que la precarga, por lo que es posible que la personalización ya se conozca en este punto y que los cambios (por ejemplo, navegar por otros productos o iniciar o cerrar sesión) requieran a menudo una nueva carga de la página y, por tanto, una nueva precarga, que los tendrá en cuenta. Pero sin duda es algo que hay que tener en cuenta y probar. Las páginas en precarga pueden cancelarse eliminando el elemento <code><script></code> de las reglas de especulación de la página mediante las API de DOM de JavaScript estándar en caso de que sea necesario cuando cambie el estado sin que se cargue una nueva página. You have to log in to edit this translation. Meta Discussion Others Status: current Added: 2025-02-06 09:59:38 UTC Translated by: Fernando Tellado (fernandot) Priority of the original: normal Translation Memory Other locales History
	Speculating with the default <code>moderate</code> eagerness decreases the risk that the prerendered page will not be visited by the user and therefore will avoid any side effects of loading such a link in advance. In contrast, <code>eager</code> speculation increases the risk that prerendered pages may not be loaded. Alternatively, the plugin offers to only speculate on mouse/pointer down (conservative) which reduces the risk even further and is an option for sites which are concerned about this, at the cost of having less of a lead time and so less of a performance gain.	La especulación con la anticipación <code>moderada</code> por defecto disminuye el riesgo de que la página en precarga no llegue a ser visitada por el usuario y, por lo tanto, evitará cualquier efecto secundario de cargar dicho enlace por adelantado. Por el contrario, la anticipación <code>ansiosa</code> aumenta el riesgo de que las páginas en precarga no se carguen. Alternativamente, el plugin ofrece especular sólo cuando el ratón o el puntero están pulsados (conservador), lo que reduce el riesgo aún más y es una opción para los sitios que están preocupados por esto, a costa de tener menos tiempo de espera y por lo tanto menos ganancia de rendimiento.	Details
Original current Permalink to translation Translation History View original in consistency tool Discussion Speculating with the default <code>moderate</code> eagerness decreases the risk that the prerendered page will not be visited by the user and therefore will avoid any side effects of loading such a link in advance. In contrast, <code>eager</code> speculation increases the risk that prerendered pages may not be loaded. Alternatively, the plugin offers to only speculate on mouse/pointer down (conservative) which reduces the risk even further and is an option for sites which are concerned about this, at the cost of having less of a lead time and so less of a performance gain. Speculating with the default <code>moderate</code> eagerness decreases the risk that the prerendered page will not be visited by the user and therefore will avoid any side effects of loading such a link in advance. In contrast, <code>eager</code> speculation increases the risk that prerendered pages may not be loaded. Alternatively, the plugin offers to only speculate on mouse/pointer down (conservative) which reduces the risk even further and is an option for sites which are concerned about this, at the cost of having less of a lead time and so less of a performance gain. Comment Found in faq paragraph. La especulación con la anticipación <code>moderada</code> por defecto disminuye el riesgo de que la página en precarga no llegue a ser visitada por el usuario y, por lo tanto, evitará cualquier efecto secundario de cargar dicho enlace por adelantado. Por el contrario, la anticipación <code>ansiosa</code> aumenta el riesgo de que las páginas en precarga no se carguen. Alternativamente, el plugin ofrece especular sólo cuando el ratón o el puntero están pulsados (conservador), lo que reduce el riesgo aún más y es una opción para los sitios que están preocupados por esto, a costa de tener menos tiempo de espera y por lo tanto menos ganancia de rendimiento. You have to log in to edit this translation. Meta Discussion Others Status: current Added: 2025-02-06 09:59:53 UTC Translated by: Fernando Tellado (fernandot) Priority of the original: normal Translation Memory Other locales History
	<a href="https://developer.chrome.com/docs/web-platform/prerender-pages">Information on document rules syntax support used by the plugin</a>	<a href="https://developer.chrome.com/docs/web-platform/prerender-pages">Información sobre la sintaxis de las reglas de documentos que utiliza el plugin</a>	Details
Original current Permalink to translation Translation History View original in consistency tool Discussion <a href="https://developer.chrome.com/docs/web-platform/prerender-pages">Information on document rules syntax support used by the plugin</a> Comment Found in description list item. <a href="https://developer.chrome.com/docs/web-platform/prerender-pages">Información sobre la sintaxis de las reglas de documentos que utiliza el plugin</a> You have to log in to edit this translation. Meta Discussion Others Status: current Added: 2025-02-06 10:00:33 UTC Translated by: Fernando Tellado (fernandot) Priority of the original: normal Translation Memory Other locales History
	For client-side JavaScript, is recommended to delay these until the prerender is activated (for example by clicking on the link). Some solutions (like Google Analytics) already do this automatically, see <a href="https://developer.chrome.com/docs/web-platform/prerender-pages#impact-on-analytics">Impact on Analytics</a>. Additionally, cross-origin iframes are not loaded until activation which can further avoid issues here.	En el caso de JavaScript del lado del cliente, se recomienda retrasarlos hasta que se active la precarga (por ejemplo, haciendo clic en el enlace). Algunas soluciones (como Google Analytics) ya lo hacen automáticamente, ve el <a href="https://developer.chrome.com/docs/web-platform/prerender-pages#impact-on-analytics">impacto en Analytics</a>. Además, los iframes de origen cruzado no se cargan hasta su activación, lo que puede evitar problemas en este caso.	Details
Original current Permalink to translation Translation History View original in consistency tool Discussion For client-side JavaScript, is recommended to delay these until the prerender is activated (for example by clicking on the link). Some solutions (like Google Analytics) already do this automatically, see <a href="https://developer.chrome.com/docs/web-platform/prerender-pages#impact-on-analytics">Impact on Analytics</a>. Additionally, cross-origin iframes are not loaded until activation which can further avoid issues here. For client-side JavaScript, is recommended to delay these until the prerender is activated (for example by clicking on the link). Some solutions (like Google Analytics) already do this automatically, see <a href="https://developer.chrome.com/docs/web-platform/prerender-pages#impact-on-analytics">Impact on Analytics</a>. Additionally, cross-origin iframes are not loaded until activation which can further avoid issues here. Comment Found in faq paragraph. En el caso de JavaScript del lado del cliente, se recomienda retrasarlos hasta que se active la precarga (por ejemplo, haciendo clic en el enlace). Algunas soluciones (como Google Analytics) ya lo hacen automáticamente, ve el <a href="https://developer.chrome.com/docs/web-platform/prerender-pages#impact-on-analytics">impacto en Analytics</a>. Además, los iframes de origen cruzado no se cargan hasta su activación, lo que puede evitar problemas en este caso. You have to log in to edit this translation. Meta Discussion Others Status: current Added: 2025-02-06 10:01:38 UTC Translated by: Fernando Tellado (fernandot) Priority of the original: normal Translation Memory Other locales History
	Prerendering can affect analytics and personalization.	La precarga puede afectar a la analítica y la personalización.	Details
Original current Permalink to translation Translation History View original in consistency tool Discussion Prerendering can affect analytics and personalization. Comment Found in faq paragraph. La precarga puede afectar a la analítica y la personalización. You have to log in to edit this translation. Meta Discussion Others Status: current Added: 2025-02-06 10:02:01 UTC Translated by: Fernando Tellado (fernandot) Priority of the original: normal Translation Memory Other locales History

Legend:

Current

Waiting

Rejected

Fuzzy

Old

Changes requested

With warnings

← 1 2 3 … 6 →

Export as

Translation of Stable Readme (latest release): Spanish (Spain)

Original current

Original current

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original untranslated

Original current

Original current

Original current

Original current

Original current

Original current

Original current

Original current