/ Register

Want to subscribe to topics you're interested in?
Become a Member

Cloudflare 500+ milliseconds saving for www/non-www redirects

Discussion in 'Domains, DNS, Email & SSL Certificates' started by rdan, Sep 1, 2019.

Previous Thread Next Thread
Loading...
  1. Sep 1, 2019 #1
    rdan

    rdan Well-Known Member

    5,452
    1,418
    113
    May 25, 2014
    Ratings:
    +2,212
    Local Time:
    12:11 PM
    Mainline
    10.2
    Small tip that can save 500+ms for redirect request.
    Instead of doing your www/non-www redirect on the Server level,
    just do it on Cloudflare Page Rule Instead.

    Sample for www redirect
    upload_2019-9-1_3-33-43.png

    My http to HTTPS redirect is already done by browser HSTS Preload List (local redirect 1ms).

    Test before and after via Browser Network Tab.
    With this option check
    upload_2019-9-1_3-36-46.png
     
  2. Sep 1, 2019 #2
    eva2000

    eva2000 Administrator Staff Member

    58,893
    12,490
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,122
    Local Time:
    2:11 PM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    Yes it helps but
    1. 301 redirects are cached at browser level, so subsequent 301 redirects won't hit your server anyway and come from web browser of visitor
    2. HSTS Preload enabled sites also will have redirect to HTTPS done at web browser level.
     
  3. Sep 1, 2019 #3
    rdan

    rdan Well-Known Member

    5,452
    1,418
    113
    May 25, 2014
    Ratings:
    +2,212
    Local Time:
    12:11 PM
    Mainline
    10.2
    I do have 65% of visitors that came from search engine and other site, still it helps for 1st time visitor.
    Or linked/bookmark url without www.

    That's why I don't include https redirect.
     
  4. Sep 1, 2019 #4
    eva2000

    eva2000 Administrator Staff Member

    58,893
    12,490
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,122
    Local Time:
    2:11 PM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    indeed that is where you'd have the most benefit :)
     
  5. Sep 2, 2019 #5
    jcat

    jcat Member

    154
    22
    18
    Jun 21, 2015
    New Jersey
    Ratings:
    +65
    Local Time:
    12:11 AM
    That's crazy it takes 500ms for your server to redirect, are you sure nginx was doing the redirect and not WordPress? If you are not redirecting via nginx then yes WordPress is very slow since it requires PHP to process the request, its basically like waiting for a page to load without cache.
     
  6. Sep 3, 2019 #6
    rdan

    rdan Well-Known Member

    5,452
    1,418
    113
    May 25, 2014
    Ratings:
    +2,212
    Local Time:
    12:11 PM
    Mainline
    10.2
    Not my server but...
    User > Cloudflare > My Server > back to Cloudflare > to User = Takes 600-700+ms usually.

    Without cache/First time visitor.
     
  7. Sep 3, 2019 #7
    rdan

    rdan Well-Known Member

    5,452
    1,418
    113
    May 25, 2014
    Ratings:
    +2,212
    Local Time:
    12:11 PM
    Mainline
    10.2
    With this implementation, I only got:
    User > Cloudflare > back to User = Takes 40-150 ms usually.
     
    Last edited: Sep 3, 2019
  8. Sep 3, 2019 #8
    pamamolf

    pamamolf Well-Known Member

    4,125
    429
    83
    May 31, 2014
    Ratings:
    +841
    Local Time:
    7:11 AM
    Nginx-1.29.x
    MariaDB 10.6.x
    On your screenshot you are using https or is it as an example only?

    Or do you mean that you are not using it on the server?
     
  9. Sep 3, 2019 #9
    rdan

    rdan Well-Known Member

    5,452
    1,418
    113
    May 25, 2014
    Ratings:
    +2,212
    Local Time:
    12:11 PM
    Mainline
    10.2
    I mean I do not create/include HTTP to HTTPS redirect on Page Rule.
    As it's already taken care of by browser HSTS Preload List (local redirect 1ms).
     
Previous Thread Next Thread
Loading...

.