WWW ili Nema WWW i Pagespeed

www

Posljednjih nekoliko mjeseci radim na poboljšanju vremena učitavanja stranice svoje stranice. To radim kako bih poboljšao cjelokupno korisničko iskustvo, kao i kako bih pomogao svojoj optimizaciji za tražilice. Pisao sam o nekim metodama koje sam koristio ubrzavanje WordPressa, ali također sam promijenio hosting tvrtke (u Medijatemple) i implementiran Amazonov S3 usluge za hosting mojih slika. Također sam upravo instalirao WP Super Cache na preporuku prijatelja, Adam Small.

Radi. Prema Konzola Google pretraživanje, moja učitavanja stranica smanjila su se u skladu s preporukama Google Webmastera:
www-pagespeed.png

Google vam također omogućuje da postavite zadane postavke za to hoće li vaše web mjesto postaviti izravno na www.domain ili bez www. Tu stvari postaju zanimljive. Ako promatram vrijeme učitavanja stranice bez www-a, fantastično su. Međutim, ako pogledam vrijeme učitavanja stranica s www, oni su užasni:
www-pagespeed.png

Ironija je naravno u tome što hosting paket koji uvijek imam ide na a www stranica. Zbog velike razlike u Googleovim vremenima odgovora, podesio sam konfiguraciju web lokacije na adresu koja nije www u Google Search Consoleu. Također sam uklonio kôd za preusmjeravanje iz korijena moje stranice u .htaccess datoteci koja je preusmjeravala zahtjeve koji nisu s www na www domenu.

Nisam siguran pomaže li nešto od ovoga ili boli, ali čini se logičnim. Neka ideja?

8 Komentari

  1. 1

    This is very interesting! I always redirect my websites to the WWW version for consistency and to give Google a single URL to index so rankings are not split. I also think it looks better and more balanced to the eye to force the WWW version to display. Your data, however, makes a compelling argument to re-think this. I would be curious to see your SEO results after some time. I would love it if you would share them here after some testing.

  2. 2

    Odd…just now I was reading another post and wondering why the page was taking so long to load. Looks like cdn.js-kit something was taking forever. According to your graphs, ooks like whatever you did is helping!

  3. 3

    That’s my commenting package, Joshua! I’ve seen some lag with their service as well and may have to say something soon.

  4. 4

    Will be glad to share any stats Michael! Once again, though, everyone IS going to the “www” address so I’m not sure why Google bots are slow to get access that route. Wondering if its a nameserver issue with my hosting or an apache setting or something.

  5. 5

    Yahoo! recommends using WWW. to allow for non-www. static image domains:

    <blockquote cite=”http://developer.yahoo.com/performance/rules.html#cookie_free”>If your domain is http://www.example.org, you can host your static components on static.example.org. However, if you’ve already set cookies on the top-level domain example.org as opposed to http://www.example.org, then all the requests to static.example.org will include those cookies. In this case, you can buy a whole new domain, host your static components there, and keep this domain cookie-free. Yahoo! uses yimg.com, YouTube uses ytimg.com, Amazon uses images-amazon.com and so on.</blockquote>

    Ever since reading this, I’ve gone with http://www….because Yahoo! is pretty smart.

    This is the first I’ve heard of any www speed issues. Anyone else have the same experience?

  6. 6
  7. 7

    I force with the no “WWW” so my domain is simply my name. I haven’t really tested it for speed reasons, but anytime you visit my site you get the no “WWW.”

    I looked at it from a branding perspective. I think for businesses – the “WWW” puts a perception of dependability.

    I’m half-tempted to test for speed myself. I have noticed my site loads pretty quickly on a regular basis. Coincidence?

  8. 8

Što vi mislite?

Ova web stranica koristi Akismet za smanjenje neželjene pošte. Saznajte kako se podaci vašeg komentara obrađuju.