Slashdot Mirror


Average Web Page Approaches 1MB

MrSeb writes "According to new research from HTTP Archive, which regularly scans the internet's most popular destinations, the average size of a single web page is now 965 kilobytes, up more than 30% from last year's average of 702KB. This rapid growth is fairly normal for the internet — the average web page was 14KB in 1995, 93KB by 2003, and 300KB in 2008 — but by burrowing a little deeper into HTTP Archive's recent data, we can discern some interesting trends. Between 2010 and 2011, the average amount of Flash content downloaded stayed exactly the same — 90KB — but JavaScript experienced massive growth from 113KB to 172KB. The amount of HTML, CSS, and images on websites also showed a significant increase year over year. There is absolutely no doubt that these trends are attributable to the death throes of Flash and emergence of HTML5 and its open web cohorts." If you have a personal home page, how big is it?

40 of 319 comments (clear)

  1. How Big? by Anonymous Coward · · Score: 5, Funny

    That's rather personal.

    1. Re:How Big? by Pharmboy · · Score: 5, Insightful

      Well, I don't mind bragging about mine. I was 100k, but now has swollen to 150k this year. As to *real* servers, I try to keep our ecommerce pages below 250k for gateway pages. Until this year, I tried to keep them under 150k. Up until 2008, 100k was the target. Before 2003, 50k. This is kind of light, and a few pages bust this, but very few. Before 2000, I used to spend lots of time just optimizing graphics, now I just use some common sense, PS, and very little time.

      What I have found is that the total k of data isn't as important as the number of items and hosts the page calls. I find I can make my pages faster by using image maps, which make larger images size (12 images 1 image of all 12 items) but load faster because it takes less connects. There are a few tools online that can help you figure out total load times. Nowadays, load time is NOT purely a function of the size of the data. If you can cut down on the number of GETS and cross domain GETS (ie: DNS lookups) you can radically cut down load time and reliability.

      Also, pages that don't need to be dynamic, shouldn't be. Our gateway (to product categories) pages are generated as we update the site, and stored static. This allows them to be cached. It sounds old fashioned, but the fact is that it greatly increases perceived latency. I am amazed at how many websites are generated via PHP and SQL on the fly, yet aren't updated more than a couple times a day or less. That is a lot of wasted CPU cycles on the server, and a lot of wasted potential for caching, both locally and down the line. And yes, it makes your website load slower, making it seem like your pages are larger than they are.

      --
      Tequila: It's not just for breakfast anymore!
    2. Re:How Big? by buchner.johannes · · Score: 3, Informative

      With a good caching engine, dynamically generated webpages should be nearly as fast as a static page - the page it's self is parsed and cached, then only re-parsed if the input changes.

      The Linux kernel can take a file and put it on the socket without Apache loading it even partially into memory. *This* is fast.

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    3. Re:How Big? by Pharmboy · · Score: 3

      No rational ecommerce site designs for a 1920 wide screen. You always design for the lowest common denominator. Most customers aren't computer geeks, and you want everyone's money, not just the smart peoples. Personal websites (the topic of the story) yes, but never for money making websites. We still design around a maximum width of 900 pixels (menus plus 760px of actual content), and will for some time. This allows for for scroll bars and a little buffer on a 1024x768 screen, or for half of a 1080p screen. It also makes it readable from tablets and phones without having multiple code bases, which is prohibitively expensive for a small to medium sized ecommerce site.

      --
      Tequila: It's not just for breakfast anymore!
  2. can't wait to see these on my phone! by Anonymous Coward · · Score: 5, Insightful

    It's a good thing phone carriers don't limit your data consumption....

    oh wait..

    1. Re:can't wait to see these on my phone! by MichaelSmith · · Score: 3, Informative

      The browser on my phone crashes on pages that size, including most articles on slashdot, so the data it uses is somewhat self limiting.

    2. Re:can't wait to see these on my phone! by hipp5 · · Score: 3, Interesting

      The phone issue is interesting. I was just on the "How Much Data Do You Need?" page for a local provider. You slide the bar for various things, like how many web pages you visit in a month (as if anyone really knows that). Their assumption was 0.17MB/page. I know there are mobile versions of pages and such, but this still seems like a gross underestimate given this story.

  3. Not surprised by kannibal_klown · · Score: 4, Insightful

    With the growth of Javascript libraries like JQuery for more UI features, more images, I can see it reaching that high.

    Meanwhile, web developers don't care because more and more people are getting faster and faster broadband speeds. So as long as the page-load metric works OK on their rig or perhaps what the envision most of their viewers have... they think it's all OK.

    1. Re:Not surprised by Fujisawa+Sensei · · Score: 4, Insightful

      Apparently it is because users are still hitting their websites.

      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    2. Re:Not surprised by Anonymous Coward · · Score: 5, Insightful

      Web developers don't care because the majority of their images/css/js is cacheable by each visitor (and most people have jQuery cached from the official site and many sites link to that directly). 1MB page but it's only 45k on the next visit.

    3. Re:Not surprised by TheSpoom · · Score: 4, Informative

      Yup. Google helps us out here. If we're using offsite resources like that, there's a fair likelihood that it's cached in the user's browser even if it's the first time they've visited the site.

      --
      It's better to vote for what you want and not get it than to vote for what you don't want and get it.
      - E. Debs
    4. Re:Not surprised by Threni · · Score: 4, Interesting

      Forgive me piggybacking here, but I've a web question. I read Slashdot predominantly on my phone (doesn't everyone?), but once you get 5 or 6 levels of replying in, the posts become unreadable. Each reply has a shorter width then the one above, meaning you end up with a handful of characters per line, and the rest of the horizontal space as just that - space. Is that really how it's supposed to be - completely unreadable? Is there no way of overriding it and saying 'look, I know it's a reply due to the context`. I've tried poking around in the various options within Slashdot, but I don't understand what most of them do, and the so-called help is completely useless and doesn't describe what the options mean nor how to use them. I think the problem is that the designers of Slashdot believe everyone is using a monitor so you'd probably need to be about 30 or 40 levels in to get to the same problem.

      I'm using Dolphin HD on Android but a friend with an Apple phone has the same problem. Is there an answer?

    5. Re:Not surprised by webnut77 · · Score: 5, Insightful

      Yup. Google helps us out here. If we're using offsite resources like that, there's a fair likelihood that it's cached in the user's browser even if it's the first time they've visited the site.

      And then Google also gets to look at the referrer data.

    6. Re:Not surprised by matmota · · Score: 3, Insightful

      First select the "classic discussion system (D1)" under "Discussions" in your options (gear icon). Then, in the settings just below the summary pick the "flat" view instead of "nested".

  4. Missing data by instagib · · Score: 5, Interesting

    Average information content - does a page view give me more insight as a user now than it did 10 years ago?

    1. Re:Missing data by Anonymous Coward · · Score: 5, Insightful

      10 years ago online video was virtually nonexistent, and where it did exist it was never larger than 320x240. Pictures were equally low resolution and page formatting was minimal. Allowing user comments was rare, and user contribution based sites like YouTube and Wikipedia were nonexistent. Oh yea, and the "blink" tag was still popular. So yes, I would say the amount of information has increased significantly.

  5. Please remember the dial-up users... by MetricT · · Score: 4, Informative

    and the 3G users, and the satellite users, and everyone else that has a low-bandwidth and/or high cost per byte connection.

    My parents can't get DSL or cable. They're stuck with 22k dial-up, and use AdBlock Plus, NoFlash, and Propel accelerator with compression set to the point where you can barely recognize photos, and it still takes 2 minutes for a reasonably normal page (CNN, MSNBC) to load, much less anything with a ton of Javascript or Flash.

    Can't websites automatically detect connection speed the first time a client visits, and store a cookie so that us slow people get a nice, simple website?

    Oh, and Propel, please move to JPEG2000 and XZ compression. Some people need every byte they can get.

  6. Size Doesn't Matter by stating_the_obvious · · Score: 4, Funny

    It's not the size of the home page, it's the motion of the .GIF

  7. Ads by Anonymous Coward · · Score: 5, Interesting

    And.... when running AdBlock Plus, this figure goes down to 100kB. I run AdBlock mostly for the massive speed increase that comes with it.

  8. If you have a homepage by burning-toast · · Score: 3, Insightful

    I have a homepage, and it's only 4.92Kb. Granted it is the "It Works!" page for CentOS which has all of the other text and icons and such but who needs more than that? Do people really have personalized home pages now that Facebook came about (other than some hobbyists or professionals who run a side business)?

    I wonder what the average "Facebook" homepage size is... since that is what most people will be seeing regularly.

    - Toast

  9. Compression? by s7uar7 · · Score: 3, Insightful

    If the bulk of the increase is from javascript wouldn't turning on compression on the web server solve the problem? They're text files, they compress down massively.

    1. Re:Compression? by TheSpoom · · Score: 4, Interesting

      Yes, compression helps (and is generally done automatically in any good Apache configuration). What helps even more from a user's perspective is combining files; basically, in the backend we combine all our Javascript and CSS (or as much as is reasonable) into one file instead of serving it as multiple, separate files linked to the current page. This cuts down on HTTP requests massively and speeds site loading from a user's perspective. Yahoo has a great list of best practices for speeding up sites if you're interested.

      --
      It's better to vote for what you want and not get it than to vote for what you don't want and get it.
      - E. Debs
    2. Re:Compression? by mollymoo · · Score: 3, Interesting

      Persistent HTTP connections were tacked on to HTTP 1.0 years ago and are widely supported, but you still have the "can I have that bit now please?" overhead with the associated latency between retrieving each file on each connection. 100ms of latency multiplied by a dozen assets soon adds up. HTTP 1.1's pipelining means you can ask for many things at once so only suffer that hit once (or twice - page then assets), but in practice browser support for pipelining is poor.

      --
      Chernobyl 'not a wildlife haven' - BBC News
  10. Larger Pages by Master+Moose · · Score: 5, Insightful

    And Less Content. .

    I remeber the days when a site would include an 10 paragraph article on one page - Not 10 pages with a paragraph on each.

    --
    . . .gone when the morning comes
  11. Flawed methods ... by oneiros27 · · Score: 4, Interesting

    This only matters if people go to the first page, and never go to any additional ones.

    For most websites these days, you'll take the initial hit from javascript and the 'branding' images when you first get to the site ... but the changing content per page is much lower.

    If websites are using standard javascript libraries being served by Google's CDN, then it's possible that someone visiting your page already has jquery, mootools or similar cached and doesn't need to load yet another copy.

    I also didn't see if they had any comparison between transferred size vs. used size. (eg, javascript that's sent compressed) ... and as this is from an new archive ... does anyone know if Archive.org could analyze their holdings to see what the longer term trends are?

    --
    Build it, and they will come^Hplain.
  12. Now I can feel smug by rbrander · · Score: 4, Insightful

    My home page remains where it has been since 1993 at the Calgary Unix Users Group: http://www.cuug.ab.ca/branderr ...clocks in at 9.2K, plus a 15K GIF and a 9.1K JPG (if you "turn on images" in your browser - remember when it was a realistic option not to?)

    I have held the line, while Viewing With Alarm (VWA) the growth of web pages for the entire 18 years since. I wrote Bob Metcalfe when he had a column at InfoWorld 15 years back, and he was Viewing With Alarm the exponential growth in Internet traffic and predicting the "collapse of the Internet" (had to eat those words - literally) because of it. My letter pointed out that his column constituted 2K of text - that was all the generated content that was bringing in the readers, (unless you count the 10K gif of Bob Metcalfe, and I don't), and the page had an additional 100K of framing and advertising-related image GIFs. His reply was somewhat defensive.

    This last year, I had occasion to travel on the Queen Mary 2, where all internet is via satellite at a minimum of 34 cents per minute with their bulk plan. How quickly I grew to resent the giant Flash blobs that would be automatically downloaded with every page of a newspaper so I wouldn't miss the animated ads for the latest in car buys. At QM2 speeds, I'd have to wait about two minutes before I even had an "X" mark to click on to dismiss the ad. I was rather quickly cured of almost any interest in the Internet content at ALL, I did my E-mail, checked the google news headlines (fewest high-byte ads), and logged off.

    My point: 90% of mail is spam. So are 90% of web page bytes. We just don't call it spam. We call it "the whole outside frame around the news page that we try not to see, but keeps jumping around into our field of view".

    1. Re:Now I can feel smug by whisper_jeff · · Score: 3, Interesting

      Sorry to be a dick but you're bragging about that page? Really? You know when they say "size doesn't matter"? Yeah - sometimes it also means being as small as possible is not necessarily a good thing. I would have thought that page was trash ten years ago when Geocities webpages were everywhere so, now, it's really not good... Seriously, stop bragging about it and spend some time designing a real page.

      Sorry to be a dick - someone had to tell you...

  13. No, it's not HTML5. It's just junk. by Animats · · Score: 5, Insightful

    There is absolutely no doubt that these trends are attributable to the death throes of Flash and emergence of HTML5 and its open web cohorts.

    No, it's not about HTML 5. A lot of it is about bloated content management systems and templates.

    I was looking at a Wall Street Journal page recently, and I brought it into an HTML editor so I could eliminate all non-story content. The story required an HTML page with only 72 lines. The original page was over 4000 lines. It contained a vast amount of hidden content, including the entire registration system for buying a subscription. All that junk appears on every page.. Inline, not in an included file.

    On top of that, there are content management systems which create a custom CSS page for each content page. So there's no useful caching in the browser.

    Remember those people who said CSS was going to make web pages shorter? They were wrong. Look at Slashdot - bloated, slow pages that don't do much, yet consume CPU time when idle.

    1. Re:No, it's not HTML5. It's just junk. by Desler · · Score: 4, Insightful

      But Slashdot is now web 2.0, Ajax-enabled and social. Pretty soon it'll be "hosted on the cloud" and provide SaaS so it can win at buzzword bingo!

    2. Re:No, it's not HTML5. It's just junk. by rubycodez · · Score: 3, Insightful

      let's just use 1 acronym for all that, BWC. Bloated Web Crapware

  14. Re:Ad Content by Idbar · · Score: 4, Funny

    My webpage is just about 1k. But you have you watch a 30 sec. interlaced Bluray quality ad before you can see it.

  15. 90KB of Flash by Anonymous Coward · · Score: 4, Funny

    That's still too much flash for me

    Sent from my iPhone

  16. Video sucks. by PeanutButterBreath · · Score: 4, Insightful

    10 years ago online video was virtually nonexistent, and where it did exist it was never larger than 320x240.

    And now it is ubiquitous, HD and largely devoted to pointless things that would be skimmed over and disregarded in a fraction of the load time if left to text and still images.

    1. Re:Video sucks. by Tumbleweed · · Score: 4, Insightful

      TubeCat disagrees with everything about what you just said.

  17. Re:Hallelujah by rwise2112 · · Score: 4, Funny

    That's what she said!

    --

    "For every expert, there is an equal and opposite expert"
  18. Am I the only one reminded of.... by LiquidMind · · Score: 4, Interesting

    http://www.the5k.org/

    It seemed so long ago. Didn't /. have an entry as well?

    --
    This sig contains repetition and redundancy.
  19. Too much Javascript for non-interactive content by rollingcalf · · Score: 3, Informative

    Some sites use Javascript to display what is semi-static data that should be assembled on the server side before transmitting to the user. For example, a news site where the stories are loaded by Javascript.

    Some sites even have pages that are entirely blank if Javascript is turned off. It seems that some of these "web programmers" don't even know how to dynamically build a page with server-side scripting instead of Javascript.

    --
    ---------
    There is inferior bacteria on the interior of your posterior.
  20. Re:Hallelujah by g0bshiTe · · Score: 5, Funny

    It's not the size of your homepage, it's how you use it.

    --
    I am Bennett Haselton! I am Bennett Haselton!
  21. Re:... and it also sucks. by mickwd · · Score: 3, Insightful

    "In short: You fail web page design, so who the fuck cares if your page is 10K?"

    As a normal human being possessing the ability to read, I found his site perfectly accessible, and it gave me a decent amount of information about the guy in a quick, concise manner.

    If I was to be snarky here, I would say something like:

    In short: You fail meaningful criticism, and who the fuck cares if his "anchors span multiple sentences rather than just a few semantically relevant key words"?

  22. Lies, damned lies, statistics by adolf · · Score: 3, Interesting

    So a web page today is about 10x bigger than it was in 2003. I can accept that.

    But in 2003, I had a baseline 2-megabit-per-second Internet connection and could have had a 3- or 5-megabit connection for a bit more cash.

    Today, 8 years later, the "normal" connection speed for my ISP is 6-megabit.

    So according to my observations and their statistics, folks are expected to download 10 times the amount of stuff using just 3 times as much available bandwidth.

    In other words, the web is currently more than three times slower than it was in 2003.

    Hooray!