Author Topic: any negative seo consequences with bootstrap?  (Read 8375 times)

rcjordan

  • I'm consulting the authorities on the subject
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8481
  • Debbie says...
    • View Profile
any negative seo consequences with bootstrap?
« on: March 15, 2013, 01:43:37 AM »
i've run up the new site to #2 & 3 slots using a flat, static template. Looking through the html, bootstrap looks pretty good for seo.  I'm a little concerned about load speed because this sucker is heavy even with the .min files.  I've hot-swapped the template on the file in #3 slot to bootstrap today and will watch that.  But it's worth asking about here. Any problems?

ergophobe

  • Inner Core
  • Hero Member
  • *
  • Posts: 5013
    • View Profile
Re: any negative seo consequences with bootstrap?
« Reply #1 on: March 15, 2013, 04:55:03 PM »
I don't know about bootstrap - haven't used it yet.

But I have been tuning a site with massive JS and CSS load and found that by implementing asynchronous loading of the JS, I can get the meat of the page to show quickly. You can't asynchronously load anything that uses document.write, but almost anything else can.

Obviously the total page weight is the same, in fact even a few KB bigger because now I have an asynchronous loader on the page too, but there have been several comments about it feeling zippier for the users. So it should help with SEO both in terms of response times for Googlebot and for user engagement metrics.

I don't know offhand if Bootstrap loads asynchronously by default or not, but it should be easy enough to add if not.

rcjordan

  • I'm consulting the authorities on the subject
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8481
  • Debbie says...
    • View Profile
Re: any negative seo consequences with bootstrap?
« Reply #2 on: March 15, 2013, 05:53:53 PM »
Thanks.  I know less-than-jack about async but I'm going to have to do something.

This looks promising

http://headjs.com/

found here:
http://webification.com/12-javascript-loaders-to-speed-up-your-web-applications

Also noteworthy (if correct) "iPhone 3.x cannot cache files larger than 15kb and in iPhone 4 the limit is 25kb. And this is the size before gzipping. if you care about iPhones you should respect these limits."

ergophobe

  • Inner Core
  • Hero Member
  • *
  • Posts: 5013
    • View Profile
Re: any negative seo consequences with bootstrap?
« Reply #3 on: March 15, 2013, 11:48:06 PM »
* head.js
 - used on some bigname sites
 - not being developed anymore.
 - http://headjs.com

*scriptjs
 - http://dustindiaz.com/scriptjs - read the intro there and the article he links.
 - builds on head.js and control.js
 - has nice praise for LABjs

*LABjs
 - my choice just because it's so easy to use
 - http://labjs.com/

*ControlJS
 - Steve Souders entry, which tries to solve the document.write() problem


I've been working on related issues a fair bit lately. If you need help and I don't see this thread, give me a ping.

ergophobe

  • Inner Core
  • Hero Member
  • *
  • Posts: 5013
    • View Profile
Re: any negative seo consequences with bootstrap?
« Reply #4 on: March 15, 2013, 11:59:37 PM »

Chunkford

  • Inner Core
  • Hero Member
  • *
  • Posts: 1024
    • View Profile
Re: any negative seo consequences with bootstrap?
« Reply #5 on: March 16, 2013, 11:35:16 AM »
If it helps this framework starts from the smallest screen upwards rather than loading for the largest downwards - http://stuffandnonsense.co.uk/projects/320andup/
That should stop unnecessary elements being loaded.
"If my answers frighten you then you should cease asking scary questions"

ergophobe

  • Inner Core
  • Hero Member
  • *
  • Posts: 5013
    • View Profile
Re: any negative seo consequences with bootstrap?
« Reply #6 on: March 16, 2013, 04:48:06 PM »
That should stop unnecessary elements being loaded.

Lots of frameworks have gone mobile first, but that doesn't really address the problem here.

Media queries will only affect what CSS gets loaded. In terms of background images, most modern browsers defer loading the background images until the entire CSS cascade is loaded and they know which image they want. So order doesn't matter for that.

In terms of Javascript, the media queries won't change that at all. If it's not set up to load asynchronously, it will load as a "blocking" script and that won't change either because these frameworks are not changing the HTML (and thus the script calls) based on device size, only the CSS.

And then as for the rest of it, you can set content to display:none for mobile, but it doesn't reduce your payload.

Also, if you have a lot of corporate users stuck on IE8, a mobile first strategy presents some problems because of IE8's poor understanding of media queries. There's a huge long debate about this in the HTML5 Boilerplate community - a thread with over 100 posts and some of the well-known people participating.

https://github.com/h5bp/html5-boilerplate/issues/816

So in short, you should think of "mobile first" design (big buzzword) as a progressive enhancement strategy rather than a payload management strategy.

Because of all of this, I saw a recent article by a guy who wrote a book on mobile first design explain why he had actually built a site that had separate URLs for mobile and desktop.

jetboy

  • Inner Core
  • Sr. Member
  • *
  • Posts: 417
  • Hens of warfare!
    • View Profile
    • Email
Re: any negative seo consequences with bootstrap?
« Reply #7 on: March 17, 2013, 09:02:14 AM »
Another vote for lab.js. It works(ish) with older browsers, it's lightweight, and I've had it in production for over a year with no problems.

rcjordan

  • I'm consulting the authorities on the subject
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8481
  • Debbie says...
    • View Profile
Re: any negative seo consequences with bootstrap?
« Reply #8 on: March 30, 2013, 10:03:53 PM »
No negatives to report. The rank is holding on the more established site and I used it to leverage a new bootstrap-responsive site which rose to #12 out of 36M in a few weeks ...too soon to tell if it's going to hold, but bootstrap doesn't seem to hurt. I was hosting the libraries at the time and haven't yet installed lab.js