Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Snappy 4.7
I’m aware this sounds like blowing our own trumpet, but I just upgraded the site I’m working on for a client from 4.6.2 to 4.7.1. No other server changes whatsoever, a simple update. Server’s running on the lowest Digital Ocean droplet, with Apache, Percona and PHP 7.0.something as I haven’t updated to the latest yet.
Been working on the 4.6.2 site for a few days, modifying Pages and Forms and clicking articles to test things, and navigating the admin side yahde yahde. Was impressed with how it behaved. But wow, after the upgrade everything just feels so much more responsive. Like, a huge step up.
Sure, there were a few MB of logs which have now been zapped on update so that’ll be having a fair impact on public site performance, but overall the entire experience feels super clean and super fast on both public site and admin side.
I’m majorly proud of our success at managing to pack this many new features into Textpattern and not only keep its nimble spirit alive but also to make it more efficient and a joy to work with.
Hats off to everyone who has made 4.7 what it is. Looking forward to our next milestone.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Snappy 4.7
Yep, here’s some real-world speed testing of our homepage (which is fairly heavy due to media within) and a less-heavy (and fairly standard) blog article which bears out your own experiences:
Homepage
Blog article
And just for fun, homepages of some other CMSes as a comparison. Not too scientific, but you’d assume each was running on pretty optimal code and hardware. In order of performance. Oh dear, Drupal, oh dear (so glad I don’t have to use that CMS in my day job any more).
Offline
Re: Snappy 4.7
Yummy! Phil, where did you do those tests?
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Snappy 4.7
Offline
Re: Snappy 4.7
philwareham wrote #314020:
Yep, here’s some real-world speed testing of our homepage (which is fairly heavy due to media within) and a less-heavy (and fairly standard) blog article which bears out your own experiences:
That’s very pleasing.
Offline
Re: Snappy 4.7
Bloke wrote #314018:
I’m majorly proud of our success at managing to pack this many new features into Textpattern and not only keep its nimble spirit alive but also to make it more efficient and a joy to work with.
Hats off to everyone who has made 4.7 what it is. Looking forward to our next milestone.
Well done Stef and all you Developers and contributors. It’s a beautiful thing you’re doing.
Offline
Offline
Re: Snappy 4.7
philwareham wrote #314023:
cool. so i decided to test my site.
Report says:
The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources:
anyone have any idea how to do what is suggested?
…. texted postive
Offline
Re: Snappy 4.7
bici wrote #314058:
cool. so i decided to test my site.
Report says:
The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources:anyone have any idea how to do what is suggested?
Add in your htaccess
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access plus 1 year"
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType image/gif "access plus 1 year"
ExpiresByType image/png "access plus 1 year"
ExpiresByType text/css "access plus 15 days"
ExpiresByType text/html "access plus 10 seconds"
ExpiresByType application/pdf "access plus 1 month"
ExpiresByType application/javascript "access plus 1 month"
ExpiresByType application/x-javascript "access plus 1 month"
ExpiresByType text/javascript "access plus 1 month"
ExpiresByType application/x-shockwave-flash "access plus 1 month"
ExpiresByType image/x-icon "access plus 1 month"
ExpiresByType application/atom+xml "access plus 1 hour"
ExpiresByType application/rss+xml "access plus 1 hour"
ExpiresDefault "access plus 1 month"
</IfModule>Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Snappy 4.7
bici wrote #314058:
The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources:
anyone have any idea how to do what is suggested?
Check what’s listed under “following resources”. You can optimise that for data served from your own site but if they’re external services, I don’t think you can (correct me please someone if I’m wrong).
I get that message when using typekit and the best you can do there (I think) is extend the caching period in the typekit kit settings.
colak wrote #314059:
Add in your htaccess
There’s also a quite comprehensive list from here downwards in the HTML5 Boilerplate htaccess file.
TXP Builders – finely-crafted code, design and txp
Offline
Re: Snappy 4.7
colak wrote #314059:
Add in your htaccess
Thanks!
w00t w00t
Last edited by bici (2018-09-16 15:45:26)
…. texted postive
Offline
Re: Snappy 4.7
You could make the “Serve static content from a cookieless domain” into an A if you use the oui_cookie plugin and create a GDPR type permission.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline