Member Avatar for johnsmith486

Not sure if this is the right forum to post this. We are looking to improve the speed of our [custom website] to rank higher on google. Can anyone guide us on how this could be done?

Edited by Dani because: Spammy link snipped
  • 5 Contributors
  • 4 Replies
  • 66 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by Member #1201033

Dani AI

Generated

A focused diagnostic + targeted fixes that build on the thread

As noted, an oversized DOM and heavy client-side work are top suspects for slow page load. The replies here already point to common areas (third‑party assets, hosting and caching). The most effective next step is a measured workflow: collect both lab and field metrics, then attack the biggest main‑thread and render blockers first. Start with PageSpeed Insights and the Core Web Vitals guidance at web.dev/vitals to get a prioritized view of LCP, INP/FID and CLS.

Concrete, less-often-cited actions

  • Reduce DOM complexity: server-side render or prerender content pages, paginate or virtualize long lists, and remove theme/plugin wrappers that add nested nodes.

  • Cut main-thread JavaScript: split bundles, defer noncritical code, and lazy-load widgets so parsing and compilation are minimized.

  • Use resource hints and font best practices: preload the font(s) used in the critical render path and add font-display: swap.

    <link rel="preload" href="/fonts/inter.woff2" as="font" type="font/woff2" crossorigin>

  • Move heavy third‑party scripts off the critical path: load on idle or on interaction, or replace widgets with server-rendered snapshots.

  • Enable modern transport and compression on the server: HTTP/2 or HTTP/3 plus Brotli to reduce round trips and bytes.

Troubleshooting workflow
Run a Lighthouse trace, then use Chrome DevTools Performance and Coverage to find long tasks and unused CSS/JS; use the Third‑party summary to quantify vendor impact (Chrome DevTools docs). Fix the single largest offender, retest, then iterate. Mentioned observations from , and help prioritize audits, but the rule of thumb is: measure, fix the biggest main‑thread/render blocker, and repeat.

Recommended Answers

All 4 Replies

Member Avatar for rproffitt

Why does this site have 6,923 DOM elements? Seems excessive to the max.

Read the full report at

At 3.3 seconds you have your work cut out for you. Most of that looks self-inflicted.

Member Avatar for Member #1202103

You can reduce external HTTP requests if you have an abundance to boost your website speed. Many WordPress plugins and themes load all kinds of files from other websites. These files can include scripts, stylesheets, and images from external resources like Google, Facebook, analytics services. It could slow down your website significantly.

commented: I still want to know the answer to "Why does this site have 6,923 DOM elements?" +15
Member Avatar for Naheedmir

Following are some of the ways to improve the speed of your custom website:

  • Use LiteSpeed webserver
  • Enable Cache
  • Optimize images
  • Remove Post Revisions
Member Avatar for Member #1201033

Some of the ways to increase custom website speed are:

  1. Minimize HTTP requests
  2. Optimize CSS delivery
  3. Reduce server response time
  4. Choose the right hosting option for your needs
  5. Enable browser caching
  6. Reduce image sizes
  7. Use a CDN
  8. Use external hosting platforms
  9. Reduce the number of plugins you use on your site
  10. Monitor mobile and web page speed
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.