Before couple of days First byte time was A but now it has been F. I havenot done any changes to my server setting and website that degrades the performance. Can anybody help me to figure out what need to be done to my website to make A from F.
How can I improve start rendering time too?
https://ecoholidaysnepal.com[attachment=887][attachment=888]
Did you ever figure this out?
It looks like your big issue is that you need to serve scaled images. Get that fixed.
Serving scaled images could save 1.3MiB (91% reduction)
https://gtmetrix.com/reports/ecoholidaysnepal.com/VFlLJVI3
https://ecoholidaysnepal.com/wp-content/uploads/2019/05/holidays-to-nepal.jpg is resized in HTML or CSS from 1200x800 to 250x150. Serving a scaled image could save 137.1KiB (96% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2018/12/chitwan-jungle-safari-3-days.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 127.2KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2018/12/everest-base-camp-heli-tour.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 123.7KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2018/12/short-Annapurna-Base-camp-trekking.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 112.8KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2018/12/honey-moon-tour.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 111.5KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2018/12/rara-lake-helicopter-tour-.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 111.3KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2019/02/Everest-base-camp-luxury-trek.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 96.3KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2018/11/gokyo-lakes-trek.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 83.3KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2018/09/annapurna-base-camp-trekking.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 83.0KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2019/03/best-trekking-in-nepal.jpg is resized in HTML or CSS from 780x585 to 250x150. Serving a scaled image could save 80.7KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2018/12/nepal-luxury-view-tour.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 80.2KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2019/01/Manaslu-Circuit-Trekking.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 63.8KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2019/04/Best-day-hikes-in-Nepal.jpg is resized in HTML or CSS from 800x532 to 250x150. Serving a scaled image could save 56.7KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2018/09/kathmandu-nepal-tour.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 46.9KiB (91% reduction).
https://ecoholidaysnepal.com/wp-content/uploads/2018/09/Everest-base-camp-trekking.jpg is resized in HTML or CSS from 1200x800 to 350x233. Serving a scaled image could save 36.7KiB (91% reduction).
I agree but it is not due to image scaling. Before couple of days the image scale issue was present but first byte time was lesser.
Usually when you’ve fixed all of the regular cms issues, first byte time is related to server hardware; I would start looking at tweaks for:
Apache
Mysql/Maria
Php
dns
SSL
etc
Here’s a place that can help you get started on that.
Poor TTFB is also because the edge locations don’t have your sites content cached. ( I see your on CloudFlare )
So when you do a fresh fetch from a given speed test location, the speed test bot is basically be served the files from the nearest origin point and not necessarily the nearest cached edge point.
Looks like you’re using WordPress. If you can, consider tuning your MySQL configuration (query cache, memory allocation, et al). I’d also consider tuning your PHP configuration to ensure the opcode cache is being used, and that your install is on the latest version.
You’re also serving content over HTTPS. See if maybe you can enable HSTS for faster HTTP-to-HTTPS redirects, and consider having your site added to the HSTS preload list to effectively eliminate 301 redirect time to the secure version of your site. It appears you’re currently not doing this, but if you decide to go down this route, carefully read HSTS documentation to understand what’s involved.
Hope this helps.
how to fix TTFB ?