[wp-trac] [WordPress Trac] #51297: The new WordPress 5.5.1 create 600ms TTFB respund

WordPress Trac noreply at wordpress.org
Sun Sep 13 17:04:36 UTC 2020


#51297: The new WordPress 5.5.1 create 600ms TTFB respund
--------------------------+--------------------------
 Reporter:  123nadav      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  5.5.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  performance
--------------------------+--------------------------
Changes (by 123nadav):

 * status:  closed => reopened
 * resolution:  worksforme =>


Comment:

 Hey, how are you?
 Thank you for your tension i appreciate that.
 So... First of all, the 5.5.1 slowest in 1000 MORE, and generally your
 test shows the 5.5 is better, is MEAN I AM RIGHT, and something is wrong
 here...

 How is even possible the older version, is better from the new one?
 even in 1 point?
 is not make sense, is an upgrade or downgrade?
 something is wrong and i am sure 99.9%.

 Now measurement is from server to server.
 With your test, i see 5.5 is better already from 5.5.1...

 I recommended you will do the test on Pagespeed and not from the SSH or
 any command-line...
 we now try to solve the Pagespeed issue ( Pagespeed is the most important
 test today, any website and even WordPress need to be compiled to this
 test... ) test via command line not rendering the site is not a reasonable
 test to our problem... especially when you chack # and any server use
 nginx can provide false data or data without apache.

 if the issue is serious i even not care to purchase premium support from
 the WordPress team about
 the issue.
 ( even i know i am 100% right after all the test i did. and i am sure this
 comes from 5.5.1 core files ).

 This test you, showing me is not efficient... is not a way to test
 something like that for the Pagespeed test.

 NOW, I KNOW YOU GOING TO SAY IS THE BEST WAY TO CHACK, BUT GOOGLE CHANGE
 THE GAME, AND THE CORE TEST IS CURRENTLY NOW I THE SEARCH CONSOLE AS WELL
 CONNECTED TO THE PAGESPEED URL TEST.

 You must create 2 websites... with different THEME and with the same (3 -
 4) and test them throw page speed URL and not the browser TEST, browser
 test show sometimes HIGHER Cache result and this is not the real result of
 the WORDPRESS CORE.

 I assure you, i chack that more than several times with all my developer
 and the THEME developer ( all my site is premium plugins and premium THEME
 )

 i am a developer by myself self and i design + development all the
 websites the server and the graphic...
 you can run a test in page speed you will see i don't have even a
 warning... my sites are very advance and i work on them 3 years 24/7....
 if i come to here and open a ticket, believe me, i know WordPress 5.5 is
 better then his update in 100%.

 Please, i am asking you, if you can diagnose the issue of the core AGAIN.

 Is not possible to get 600ms more exactly after the update to 5.5.1.
 The damage is critical and DESTROY SEO and even PPC with the new POLICY of
 Google...

 Like you know already, Google, demands today to be fully optimized.
 Google even said they going to buy WordPress soon. (if not buy it already
 and i am not updated).

 We must follow google... i believe WordPress does and know that as well...

 END FOR THE FINAL  :-)

 Thank you for your attention, sorry if my English is bad and something is
 not clear.
 But is very important to me, and like i said i know 99.9% the issue is
 from the core.

 I don't care to invest in WordPress Team to fix the issue or any other
 solution.
 I love WordPress i think is the best investment can to be and if i can to
 be involved i be more then
 happy to help in something like that, with my knowledge and even with
 investment (if needed).

 Best Regards,
 Nadav Levi Yahel
 Locksmith Unit

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51297#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list