Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter VogonPoet

    (@vogonpoet)

    If it matters I’m also using W3 Total Cache, with Browser Cache on and OpCode: XCache on a Dreamhost VPS.

    Thread Starter VogonPoet

    (@vogonpoet)

    OK I have learned some more:

    • It’s not CloudFlare
    • It’s not W3 Total Cache or any other plugin
    • It’s not my choice of permalink structure
    • It doesn’t have to do with my www. settings

    I created a fresh new blog using DreamHost’s one-click installer and used Load Page Analyzer on the built-in “Hello, world!” post. Got a similar 301 redirect on this post, which does not end with a trailing slash.

    The URL for the post is, where “test1” is the blog title:

    https://www.keithhennessey.com/test1/?p=1

    Load Page Analyzer shows a redirect, but from that address to that same address, which strikes me as odd.

    Here’s the Load Page Analysis:

    https://loadimpact.com/page-analysis/www.keithhennessey.com-ab9a3451b8f3e43e2fff6ed864577215

    In this case it’s wasting “only” 316ms on the redirect, compared to >1s on my real blog, but I figure if I can solve it here I’ll save a second+ where I need it.

    What is causing the redirect? I assume it’s something in WordPress, DreamHost’s setup, or the interaction between the two, since (I think) I have eliminated all other variables.

    We’re also looking for a solution to this, 6 seconds on our end using WPWebHost.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘trailing slash redirect slowing time to first byte?’ is closed to new replies.