I’m about to improve the site speed of my own website. My site is a simple portfolio with only one site with a couple elements ( small images and text ), little bit of code and a second dynamic page with my projects on. After finishing, it felds really slow when loading so I began to improve all elements, code and media on my site to get better results ( This was a helpfull guide: https://www.editorx.com/shaping-design/amp/website-optimization-editorx ) .
But now, I’m on a point where I have everything done as good as possible.
A site speed check tells me my site is still very slow.
for example:
On Desktop, it is not the slowest but not fast enough. There are a couple of problems like a very big DOM size, a really slow server response time and some unused Java script.
Third party Code is blocking, 3G is terrible and there is something wrong with the main thread.
So, is is there everything I can do to get better results?
I think Editor X or Wix have slow servers what is very bad. I checkt a blank site with only one element with the speed test and the results are even bad.
As for the unused JavaScript, it depends on what the code its displaying but some of it may be critical to the site structure .
I will say usually for these tests, they check the sites with suboptimal conditions so it might not be a real-world representation of the site loading time.
thanks for your replay.
I got an answer from the Wix team and it looks like the speed checks simulate the user data if there isn’t enough data currently. That’s maybe a reason for the bad resalts.
I will check in the future when there is more trefic on my site.
If your site is slow even after optimizing images and layout, remaining speed issues usually come from page complexity, JavaScript execution, and third-party scripts, not basic design.
What typically helps :
Keep above- the-fold content minimal so the first render happens quickly.
Reduce JavaScript running on page load (heavy logic in onReady() or masterPage.js affects every page).
(Instead of putting everything in onReady() or masterPage.js, gate it by page:
if (!document.body.classList.contains(“home-page”)) return;
// heavy logic only runs on homepage
}
)
OR
This prevents blocking the initial render:
Avoid global event listeners and unnecessary repeaters on large pages.
Remove or replace third-party apps/scripts that inject blocking JS.
Split long or content-heavy pages into smaller pages.
Alternatively, if you want to go beyond what manual code can realistically control in Wix Studio, Website Speedy (Wix App)helps by automatically deferring render-blocking scripts and prioritizing critical assets without changing your layout or code structure.
(Disclosure: We are the developers of this tool and happy to assist you .)