Dear Sir,
If you can please advise for some improvements for a better result,
my result is: http://www.webpagetest.org/result/130805_CB_1B4H/
my website is: elmarada.org
Just from a really quick look:
1 - Do some back-end optimizing and reduce the TTFB (could be a hosting issue if you are on shared hosting). The browser can’t do anything for the 1.8 seconds before HTML starts to come back.
2 - Merge the css and js files together - Looks like there are ~24 separate requests for css and js files in the head of the page. They don’t all have to be in one file but a smaller number of logical groupings will be a lot faster.
3 - Move the js out of the head and to the end of the document (may be more difficult if you have any inline script).
4 - Merge your png graphics together into a sprite (not the photos, just the page elements).
Thanks for your answer and sorry for the delay because i didn’t know you answered so i posted new thread so you can ignore it.
i have a dedicated server, and only this domain is on it.
is first byte related to the server or to the http request on the website?
i installed jch optimization but i didn’t use it yet because it has some conflict with minify.
Dear Sir,
Please can you have a look on the test again after i minified and deffered javascript and css:
http://www.webpagetest.org/result/130819_98_ANT/1/performance_optimization/#compress_text
still have first byte very long!
any advise!
thanks in advanced
You need to fix the first byte time and external tools aren’t going to be able to tell you why it is slow (it is a black box from the outside). You need to either instrument your code or run something like New Relic to figure out why things are slow. If you are on shared hosting then it may be a problem with the hosting itself.
hi,
i am on dedicated server which has only one account.
i installed jotcache and it improved the first byte.
http://www.webpagetest.org/result/130824_K1_50K/
but it causes “session fully load” i am searching how to fix it.
do u think is it a great idea to use jotcache or should i fix the first byte with the server directly?
I’d focus on fixing the first byte time as much as possible on the server first and then when you have it humming and still want to go faster you can look at page caching. Being on a dedicated server you have a lot of very good options.
First off I’d recommend installing New Relic to get visibility into where the performance issues are (web server, application code or database) and then go from there.
It looks like you’re running Joomla on Apache. If you’re feeling up to it my recommendation would be to try nginx with php-fpm and apc (when I made the switch for WPT things got an order of magnitude faster and it can scale a hell of a lot higher). It’s possible to configure Apache to be as fast as well, just not nearly as easy as it is with nginx.
After you have that working I’d install memcache and configure Joomla to use memcache for the session cache instead of the database.
That should get the basics running quite fast and give you options for additional caching strategies (may need some mysql tuning as well).
How are you creating the images? I get a smaller file when I do a lossless conversion to progressive of your existing file: http://www.patrickmeenan.com/progressive/view.php?img=http%3A%2F%2Felmarada.org%2Fmedia%2Fk2%2Fitems%2Fcache%2Fce7135a8194dcf274f9f78793bc352ab_S.jpg
That should result in both a progressive jpeg and a smaller file than the optimizations.
The online tool uses jpegtran to create the progressive version which doesn’t change the compression, it just converts existing jpeg’s to progressive (or optimizes baseline images too).
[hr]
it worked and got A but google chrome doesn’t recognise progressive jpg? i have blank pictures on my website!