New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Enables browsers to speculatively prerender or prefetch pages to achieve near-instant loads based on user interaction. | Tarayıcıların, kullanıcı etkileşimine bağlı olarak sayfaları önceden işleyip önceden yükleyerek neredeyse anında yükleme sağlayabilmesini sağlar. | Details |
Original current
Enables browsers to speculatively prerender or prefetch pages to achieve near-instant loads based on user interaction.
You have to log in to edit this translation. |
|||
| ↑ | Speculative Loading | Spekülatif Yükleme | Details |
Original current |
|||
| Use the controls in the <strong>Speculative Loading</strong> section to configure speculative loading. | Spekülatif yükleme için <strong>Spekülatif yükleme</strong> bölümündeki denetimleri kullanın. | Details | |
Original current
Use the controls in the <strong>Speculative Loading</strong> section to configure speculative loading.
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Visit the <strong>Settings > Reading</strong> admin screen. | <strong>Ayarlar > Okuma</strong> yönetim ekranını ziyaret edin. | Details | |
Original current
Visit the <strong>Settings > Reading</strong> admin screen.
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| After activation | Ekinleştirme sonrası | Details | |
Original current |
|||
| 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. | Varsayılan olarak spekülatif yükleme yalnızca oturumu kapatmış kullanıcılar için etkindir; çünkü kimliği doğrulanmamış sayfalar genellikle yalnızca önbelleğe almaya uygundur ve bu nedenle önceden getirmek/işlemek daha verimlidir. Bu da ön yüzde sıkça oturum açmış kullanıcıları barındıran sitelerin—örneğin e-ticaret, forum ya da üyelik sitelerinin—bu özellikten yararlanamayacağı anlamına gelir. Sunucunuz ek yükü kaldırabiliyorsa (örneğin kalıcı nesne önbelleğiyle), spekülatif yüklemeyi tüm oturum açmış kullanıcılar ya da yalnızca yöneticiler için etkinleştirmeyi seçebilirsiniz. Bu ayar yalnızca ön yüz sayfalarını etkiler; yönetici ekranları her zaman hariç tutulur. | Details | |
Original current
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.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| 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. | Bu eklenti, belirli URL'lerin dinamik olarak önceden getirilmesini ya da önceden işlenmesini sağlayan kuralların tanımlanmasına olanak tanıyan <a href="https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API">Speculation Rules API</a> desteğini ekler. Bu çekirdek Spekülatif Yükleme işlevselliği <a href="https://make.wordpress.org/core/2025/03/06/speculative-loading-in-6-8/">WordPress 6.8 ile birleştirildi</a>, ancak varsayılan olarak yalnızca tutumlu bir yakınlıkla önceden getirme yapar. Buna karşılık bu eklenti, varsayılan olarak orta düzey yakınlıkla (yani bir bağlantıyla etkileşim kurulduğunda) önceden işleme yapar ve <em>Ayarlar > Okuma</em> yönetici ekranındaki "Spekülatif Yükleme" bölümünden kipi ve yakınlığı özelleştirmek için bir kullanıcı arayüzü sunar. | Details | |
Original current
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.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| 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. | Önden oluşturulan bir sayfa, onu önden oluşturan sayfaya bağlıdır; bu nedenle kişiselleştirme bu aşamada zaten biliniyor olabilir ve değişiklikler (örn. başka ürünlerde gezinme ya da oturum açma/kapatma) çoğunlukla yeni bir sayfa yüklemesi, dolayısıyla yeni bir önden oluşturma gerektirir; yeni oluşturma da bu değişiklikleri hesaba katacaktır. Ama bu kesinlikle farkında olunması ve test edilmesi gereken bir şey! Durum yeni bir sayfa yüklemesi olmadan değiştiğinde bu gerekli olursa, önden oluşturulan sayfalar, standart JavaScript DOM API'leri kullanılarak sayfadan tahmin kuralları <code><script></code> öğesi kaldırılarak iptal edilebilir. | Details | |
Original current
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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. | Varsayılan <code>moderate</code> istekliliğiyle spekülasyon yapmak, önceden oluşturulan sayfanın kullanıcı tarafından ziyaret edilmeme riskini azaltır ve böylece bu tür bir bağlantının önceden yüklenmesinin doğuracağı yan etkilerden kaçınılır. Buna karşılık <code>eager</code> ile spekülasyon yapmak, önceden oluşturulan sayfaların yüklenmeyebilme riskini artırır. Alternatif olarak eklenti, yalnızca fare/imleç basıldığında (conservative) spekülasyon yapma olanağı sunar; bu, riski daha da azaltır ve bu konuda hassas olan siteler için uygun bir seçenektir, ancak daha kısa ön hazırlık süresi ve dolayısıyla daha az performans kazanımı pahasına yapılır. | Details | |
Original current
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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: | Bu eklentiyi düzgün kalıcı bağlantıların etkin olmadığı bir sitede çalıştırıyorsanız ve durum değişikliklerine yol açabilecek kullanımda olan özel sorgu parametresi bulunmadığından eminseniz, <code>plsr_enabled_without_pretty_permalinks</code> filtresiyle spekülatif yüklemeyi etkinleştirmeyi tercih edebilirsiniz: | Details | |
Original current
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:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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. | Güvenlik nedeniyle, spekülatif yükleme özelliğinin tamamı varsayılan olarak oturum açmış kullanıcılar ve kalıcı bağlantı (pretty permalink) kullanmayan siteler için devre dışıdır. İkincisinin nedeni, eklentilerin kullanıcıların işlem yapabilmesi için sık sık özel sorgu parametreli URL'ler kullanması ve bu tür URL'lerin spekülatif olarak yüklenmemesi gerektiğidir. Kalıcı bağlantı kullanmayan sitelerde hangi sorgu parametrelerinin çekirdek varsayılanı, hangilerinin özel olduğunu ayırt etmek imkânsız ya da en azından son derece karmaşıktır. | Details | |
Original current
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Are there any special considerations for speculative loading behavior? | Spekülatif yükleme davranışına ilişkin dikkat edilmesi gereken özel durumlar var mı? | Details | |
Original current
Are there any special considerations for speculative loading behavior?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| <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">Eklentinin kullandığı belge kuralları söz dizimi desteği hakkında bilgi</a> | Details | |
Original current
<a href="https://developer.chrome.com/docs/web-platform/prerender-pages">Information on document rules syntax support used by the plugin</a>
CommentFound in description list item. You have to log in to edit this translation. |
|||
| 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. | İstemci tarafı JavaScript için bunların, prerender etkinleştirilene kadar (örneğin bağlantıya tıklanana kadar) geciktirilmesi önerilir. Bazı çözümler (Google Analytics gibi) bunu zaten otomatik olarak yapar, bkz. <a href="https://developer.chrome.com/docs/web-platform/prerender-pages#impact-on-analytics">Analitik üzerindeki etki</a>. Ayrıca çapraz kaynak (cross-origin) iframe'ler etkinleştirilene kadar yüklenmez; bu da buradaki sorunların önüne geçilmesine ek olarak yardımcı olur. | Details | |
Original current
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Prerendering can affect analytics and personalization. | Prerendering, analitiği ve kişiselleştirmeyi etkileyebilir. | Details | |
Original current
Prerendering can affect analytics and personalization.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.