The Comment loading panel decides when Disqus loads. Until then, the page carries only an empty placeholder and a small script — Disqus's own scripts, fonts and iframes aren't downloaded at all.
The default, and the right choice for most sites. Disqus starts loading once the bottom of the visitor's screen reaches the comments area, so readers who never get that far never download it.
It loads straight away instead when:
the address points at a comment — it contains #comment, as in #comments or #comment-123 — so links to a comment land on it;
the page is too short to scroll, so the visitor could never trigger it.
The lightest option: Disqus loads only for visitors who ask for it. The thread area shows a Load Comments button; clicking it shows the loading message, removes the button and loads Disqus.
A link to a comment (#comment-…) clicks the button automatically.
Choosing this method, for desktop or mobile, shows three more fields.
Extra classes for the button, separated by spaces — handy for reusing your theme's button styles, for example button wp-element-button. The button's ID is always dcl_comment_btn, so you can also target it in your own CSS.
Disqus loads with the page, like the official plugin. Use it when comments are the point of the page, or to rule out lazy loading while troubleshooting. Everything else the plugin does — counts, sync, SEO mode — still works.
Setting key:dcl_gnrl_options.dcl_type_mob · Default: empty (Same as above)
Use a different method for phones and tablets. A common setup is When comments come into view on desktop and When the visitor clicks a button on mobile, where data and battery matter more.
Mobile detection happens on the server, using WordPress's wp_is_mobile().
Page caching
Because the method is decided on the server, a page cache that stores one copy of each page serves whichever version it cached first — desktop or mobile — to everyone. If you use different methods, enable your cache's separate mobile cache, or use the same method for both.
A method added by an addon is only offered while that addon is active. If the addon is deactivated, pages fall back to When comments come into view — but your choice is kept, and comes back as soon as the addon is active again.
The plugin replaces your theme's comments area with an empty <div id="disqus_thread">, plus the button for the click method. A single script in the footer then waits for the trigger and injects https://<shortname>.disqus.com/embed.js once.
Disqus is never loaded twice, and a disqus_config function your site defines is still called, after the plugin's own — see Developer Docs.
Comment Loading
The Comment loading panel decides when Disqus loads. Until then, the page carries only an empty placeholder and a small script — Disqus's own scripts, fonts and iframes aren't downloaded at all.
Load comments
Setting key:
dcl_gnrl_options.dcl_type· Default:scrollscrollclicknormalAddons can add more — the Scroll Load addon adds As soon as the visitor scrolls.
When comments come into view
The default, and the right choice for most sites. Disqus starts loading once the bottom of the visitor's screen reaches the comments area, so readers who never get that far never download it.
It loads straight away instead when:
#comment, as in#commentsor#comment-123— so links to a comment land on it;When the visitor clicks a button
The lightest option: Disqus loads only for visitors who ask for it. The thread area shows a Load Comments button; clicking it shows the loading message, removes the button and loads Disqus.
A link to a comment (
#comment-…) clicks the button automatically.Choosing this method, for desktop or mobile, shows three more fields.
Button text
Setting key:
dcl_btn_txt· Default:Load CommentsThe button label. Plain text only — HTML is escaped. Don't leave it empty: an empty value is saved as is and the button has no label.
Show the comment count on the button
With the Advanced Buttons addon the label becomes "Load Comments (12)", and you can pick one of six ready-made button styles.
Button CSS classes
Setting key:
dcl_btn_class· Default: emptyExtra classes for the button, separated by spaces — handy for reusing your theme's button styles, for example
button wp-element-button. The button's ID is alwaysdcl_comment_btn, so you can also target it in your own CSS.Loading message
Setting key:
dcl_message· Default:Loading...Shown for a moment after the button is clicked, while Disqus loads, as
<p id="dcl_progress">.Immediately
Disqus loads with the page, like the official plugin. Use it when comments are the point of the page, or to rule out lazy loading while troubleshooting. Everything else the plugin does — counts, sync, SEO mode — still works.
On mobile devices
Setting key:
dcl_gnrl_options.dcl_type_mob· Default: empty (Same as above)Use a different method for phones and tablets. A common setup is When comments come into view on desktop and When the visitor clicks a button on mobile, where data and battery matter more.
Mobile detection happens on the server, using WordPress's
wp_is_mobile().Page caching
Because the method is decided on the server, a page cache that stores one copy of each page serves whichever version it cached first — desktop or mobile — to everyone. If you use different methods, enable your cache's separate mobile cache, or use the same method for both.
If a method's addon is switched off
A method added by an addon is only offered while that addon is active. If the addon is deactivated, pages fall back to When comments come into view — but your choice is kept, and comes back as soon as the addon is active again.
How lazy loading works
The plugin replaces your theme's comments area with an empty
<div id="disqus_thread">, plus the button for the click method. A single script in the footer then waits for the trigger and injectshttps://<shortname>.disqus.com/embed.jsonce.Disqus is never loaded twice, and a
disqus_configfunction your site defines is still called, after the plugin's own — see Developer Docs.Related