Are there any performance drawbacks when rendering DOM views at runtime with JavaScript, rather than rendering server-sent HTML?
3rd January 2012
My answer to Are there any performance drawbacks when rendering DOM views at runtime with JavaScript, rather than rendering server-sent HTML? on Quora
Yes, there is quite a significant impact on first-load performance. The browser has to pull down all of the linked scripts before it can display any content—if you’re using a library like jquery that’s a sizeable chuck of code that has to be loaded and executed just on its own.
Modern browsers may be screamingly fast at executing JS, but modern devices aren’t: mobile phones are significantly slower than desktop devices for this kind of thing.
There’s a trade-off in the other direction as well of course—if you are loading subsequent content via ajax performance on further clicks will be better than if you were doing full page refreshes.
To summarise: yes it absolutely affects performance, but that doesn’t mean you should avoid it.
More recent articles
- Slop is the new name for unwanted AI-generated content - 8th May 2024
- Weeknotes: more datasette-secrets, plus a mystery video project - 7th May 2024
- Weeknotes: Llama 3, AI for Data Journalism, llm-evals and datasette-secrets - 23rd April 2024
- Options for accessing Llama 3 from the terminal using LLM - 22nd April 2024
- AI for Data Journalism: demonstrating what we can do with this stuff right now - 17th April 2024
- Three major LLM releases in 24 hours (plus weeknotes) - 10th April 2024
- Building files-to-prompt entirely using Claude 3 Opus - 8th April 2024
- Running OCR against PDFs and images directly in your browser - 30th March 2024
- llm cmd undo last git commit - a new plugin for LLM - 26th March 2024
- Building and testing C extensions for SQLite with ChatGPT Code Interpreter - 23rd March 2024