Rapidload + Autoptimize but 4.6 seconds custom css, 4.7 REST, 5.7 initial respon
-
I bought Rapidload and got it to process the most important pages.
I emptied Autoptimize’s cache. (Not sure if that was necessary after setting up rapidload.)
Still, 9 hours later, gtmetrix’s waterfall report shows 5.7 seconds initial server response time, 4.6 seconds custom css, and 4.7 seconds for “v2” (wp-json/wp/v2) (enabling the REST API).I know my custom css is big for a custom css file – 8 kb. It’s mostly due to customizing the appearance of The Events Calendar (their settings page only allows a few changes, so everything else needed to be by custom css). But 8 kb shouldn’t take 4.6 seconds. I expect there are a few conflicts and that’s where the time goes, but shouldn’t Rapidload figure out what actually gets used and eliminate the rest?
Why is 94% of autoptimize[…].css unused? I thought rapidload was supposed to fix that. Why is 70.7% of autoptimize[…}.js unused? I thought rapidload was supposed to fix that. (On homepage. Processed by rapidload. Autoptimize cache reset, page loaded a few times between reset and measure.)
I installed the plugin Disable REST API to selectively disable for plugins that call it. Disabling all (for unauthorized users) broke my site (“unable to establish database connection”) so I enabled plugins that seemed crucial. I did not enable The Events Calendar (“tribe”). (At first check it still works.) WP-JSON v2 still takes 4.7 seconds.5.7 seconds initial server response time!? How can I find if that’s my host (Bluehost; shared) or my theme (SKT Gym, updated to version released this month; after the slowness manifested) or something else?
The backend is also crazy-making: 20 seconds to load anything. Don’t know why.
The page I need help with: [log in to see the link]
- The topic ‘Rapidload + Autoptimize but 4.6 seconds custom css, 4.7 REST, 5.7 initial respon’ is closed to new replies.