Wieviel bringt autoptimize?

Das WordPress-Plugin autoptimize soll für schnellere Ladezeiten und bessere Performance der WordPress-Seite sorgen. Um dies zu erreichen, werden alle Javascripte und CSS Dateien zusammengefasst und minifiziert.

Aber macht das in Zeiten von HTTP/2 eigentlich Sinn? Durch die Bündelung von mehreren Anfragen an den Server sollte es eigentlich keine großen Unterschiede machen, ob nun eine oder zehn Dateien angefordert werden.

Ich habe den simplen Test gemacht und den ApacheBench auf diesem Blog laufen lassen mit den folgenden Einstellungen:

ab -n 500 -kc 10 https://blog.dorianvasco.de/

Die Ausgaben zeigten, dass das aktivierte autoptimize Plugin zwar die Dateigrößen reduzierte, die Ladezeiten insgesamt aber sogar verlängerte.

autoptimize Plugin aktiviert:

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking blog.dorianvasco.de (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests


Server Software:        Apache/2.4.38
Server Hostname:        blog.dorianvasco.de
Server Port:            443
SSL/TLS Protocol:       TLSv1.2,ECDHE-RSA-AES256-GCM-SHA384,4096,256
TLS Server Name:        blog.dorianvasco.de

Document Path:          /
Document Length:        44568 bytes

Concurrency Level:      10
Time taken for tests:   42.495 seconds
Complete requests:      500
Failed requests:        2
   (Connect: 0, Receive: 0, Length: 2, Exceptions: 0)
Keep-Alive requests:    0
Total transferred:      22569998 bytes
HTML transferred:       22282498 bytes
Requests per second:    11.77 [#/sec] (mean)
Time per request:       849.891 [ms] (mean)
Time per request:       84.989 [ms] (mean, across all concurrent requests)
Transfer rate:          518.68 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:       11   33  21.6     23     110
Processing:   304  806 891.9    569    6709
Waiting:      303  803 892.0    565    6691
Total:        315  839 891.2    597    6736

Percentage of the requests served within a certain time (ms)
  50%    597
  66%    615
  75%    652
  80%    676
  90%   1523
  95%   2570
  98%   4712
  99%   5620
 100%   6736 (longest request)

autoptimize Plugin deaktiviert:

This is ApacheBench, Version 2.3 <$Revision: 1757674 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking blog.dorianvasco.de (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests


Server Software:        Apache/2.4.38
Server Hostname:        blog.dorianvasco.de
Server Port:            443
SSL/TLS Protocol:       TLSv1.2,ECDHE-RSA-AES256-GCM-SHA384,4096,256
TLS Server Name:        blog.dorianvasco.de

Document Path:          /
Document Length:        55874 bytes

Concurrency Level:      10
Time taken for tests:   35.983 seconds
Complete requests:      500
Failed requests:        0
Keep-Alive requests:    0
Total transferred:      28224500 bytes
HTML transferred:       27937000 bytes
Requests per second:    13.90 [#/sec] (mean)
Time per request:       719.658 [ms] (mean)
Time per request:       71.966 [ms] (mean, across all concurrent requests)
Transfer rate:          766.00 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:       11   33  20.6     23     105
Processing:   316  679 678.5    532    8555
Waiting:      315  675 678.8    524    8553
Total:        332  712 680.0    574    8583

Percentage of the requests served within a certain time (ms)
  50%    574
  66%    595
  75%    606
  80%    619
  90%    679
  95%   1589
  98%   2667
  99%   4614
 100%   8583 (longest request)

0

Schreibe einen Kommentar