How to speed up Html site?

TWdesigns69

Power Member
Joined
Aug 2, 2015
Messages
665
Reaction score
146
My site is static n in html css n jquery. Its speed is decent but I want it to be faster. I have lots of images and embedded cntent.
 
open your site here
https://developers.google.com/speed/pagespeed/insights/

then you can see suggestions
 
It's quite difficult to literally speed up a HTML site because it's pretty much as fast as it can get, but what you could do is:

Compress your images with https://tinypng.com/
Compress your CSS/JS/HTML with: http://refresh-sf.com/
Remove unnessesaryimages/CSS/JS from your pages

Upload everything to S3 and use CloudFront (will save you some money too)
 
open your site here
https://developers.google.com/speed/pagespeed/insights/

then you can see suggestions
It's quite difficult to literally speed up a HTML site because it's pretty much as fast as it can get, but what you could do is:

Compress your images with https://tinypng.com/
Compress your CSS/JS/HTML with: http://refresh-sf.com/
Remove unnessesaryimages/CSS/JS from your pages

Upload everything to S3 and use CloudFront (will save you some money too)

thank u. will compressing my images degrade their quality? its imp my images are of the best quality possible. also what is S3?
 
First thing - if you have a lot of embedded content, then the web loading time depends on those embedded elements. You have to move everything to your server and tune it.

Plain HTML websites are easy to optimise with server cache because they are static, unless you have a database oriented CMS. You can try CloudFlare.
 
You need to compress full site include CSS queries, Image. Before compression make sure you that you have a backup. Also, increase the server space that may also be a reason.
 
using a cdn and caching is same thing right? if i use a cdn it automatically caches for me?

It depends and no they are no the same. Caching means web server sends expiration headers with the file so static files get cached in your browser. CDN provider CAN send expiration headers, but usually expiration time comes from your web server. So next time you visit your site, your stuff loads a lot faster because static files are cached in your browser. CDN sends static files closer to your website's visitors. So for example if your site is hosted in Dallas and your CDN provider's edge node is in New York.. and a visitor from New York visits your site. Your static files are sent to your visitor from New York not from Dallas. Most CDN providers have tons of edge locations which is why it improves your website's load time.
 
It depends and no they are no the same. Caching means web server sends expiration headers with the file so static files get cached in your browser. CDN provider CAN send expiration headers, but usually expiration time comes from your web server. So next time you visit your site, your stuff loads a lot faster because static files are cached in your browser. CDN sends static files closer to your website's visitors. So for example if your site is hosted in Dallas and your CDN provider's edge node is in New York.. and a visitor from New York visits your site. Your static files are sent to your visitor from New York not from Dallas. Most CDN providers have tons of edge locations which is why it improves your website's load time.

oh ok. thank u for clarifying that. google has the most edge locations according to one article so yay!!!
 
Use lazy loading for images and iframes, your site should load instantly if it's static on a decent server. And use http://optimizilla.com/ to compress your images, I guarantee you won't see a difference in quality and it can reduce image size >50%. Hope this helps
 
Use lazy loading for images and iframes, your site should load instantly if it's static on a decent server. And use http://optimizilla.com/ to compress your images, I guarantee you won't see a difference in quality and it can reduce image size >50%. Hope this helps
thank u can u recommend a free plugin for lazy loading images and even videos
 
Lazy loading may work as well, yes, but it's possible that it's not loading everything correctly, when the visitor reaches the point where images/iframes should be loaded, which means some images/iframes may not load or lag, etc for example. I personally wouldn't go for lazy loading, but technically it will help, yes.
 
Lazy loading may work as well, yes, but it's possible that it's not loading everything correctly, when the visitor reaches the point where images/iframes should be loaded, which means some images/iframes may not load or lag, etc for example. I personally wouldn't go for lazy loading, but technically it will help, yes.
thanks. i think cdn + image compressing + cache will be enough. Will update if i see any improvement after am done. Happy holidays and thank u to everyone who helped
 
Back
Top