Re: Speeding up php.net
| From: | Hannes Magnusson | Date: | Fri, 06 Dec 2013 23:33:11 +0000 |
| Subject: | Re: Speeding up php.net | ||
| References: | 1 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-17429@lists.php.net to get a copy of this message | ||
On Fri, Dec 6, 2013 at 2:25 PM, Levi Morrison <levim@php.net> wrote:
> Dear webmasters,
>
> Several months back I worked on reducing the number of files the beta
> PHP.net needed to function. I got it down to 18 on the homepage and (I
> think) 22 for documentation pages. We are up several files since than and
> are load times are routinely over 1s.
I think UserVoice stuff and GoSquared account for a good chunk of those.
See my earlier thread about "fixing" that.
I've also reduced the initial page load by 2mb, and each page hit
after that by ~70.
> A few questions in the interest of speeding php.net up again:
>
> 1) Can we remove the elephpants? I realize are loaded later on in the
> process but they do slow things down quite a bit.
How exactly slow they anything down?
They are not in the above-the-fold content and don't block anything
> 2) Didn't we used to use static.php.net? That server seems to be a fresh
> web server installation with nothing on it. I'm not sure if serving things
> from there was ever faster but it seems to be down.
It works just fine: http://static.php.net/www.php.net/images/php.gif
I however removed. Will replace it with mirror round-robin later which
will bump how many requests the browser makes in parallel. But since
static was only used for www it wasn't very useful.
> 3) Do all servers have the ability to create new files? If they do we can
> merge the CSS files into one file and serve it instead. This can *possibly*
> be done with JavaScript files as well if we are careful.
Are you saying you want to create a file in the web dir on the fly?
No. And even if they did.. This is what we have master for.
-Hannes