# Tecnoblog's Experience With Discourse Comments

**URL:** https://meta.discourse.org/t/tecnoblogs-experience-with-discourse-comments/400721
**Category:** Feature
**Tags:** embedding
**Created:** [April 15, 2026, 6:15pm UTC](https://meta.discourse.org/t/tecnoblogs-experience-with-discourse-comments/400721 "2026-04-15T18:15:07Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [April 16, 2026, 5:21pm UTC](https://meta.discourse.org/t/tecnoblogs-experience-with-discourse-comments/400721/16 "2026-04-16T17:21:44Z")

</div>

> [@Falco](#):
>
> > [@Thiago\_Mobilon](#):
> >
> > **Lazy Loading:** Implementing lazy load for the JS helps a lot (I’m already using a workaround for this).
> 
> This is a great idea, I’m adding native support for it
> 
> [PERF: Lazy load full app embed iframe with IntersectionObserver by xfalcox · Pull Request #39299 · discourse/discourse · GitHub](https://github.com/discourse/discourse/pull/39299)

Could we use `<iframe loading="lazy">` here? That way, we don’t need custom JS or intersection observers?

---

_[View the full topic](https://meta.discourse.org/t/tecnoblogs-experience-with-discourse-comments/400721)._
