Sign in
Log inSign up

What, really, is the most data a single webpage can (should) handle?

Lila Fowler's photo
Lila Fowler
·Mar 14, 2019

It never really occurred to me until I began one of my largest website projects and started designing the structure for each page. What is the most that a single webpage should be able to handle?

For a particular page on my website (the user profile page, to be precise) I'd like to have an information packed dashboard. Some info about the page:

  1. Dashboard with live statistics
  2. Inbox with PM messages
  3. Notifications for every like and comment they received
  4. Order history (elaborate table with tons of info)
  5. Purchase history (as above)
  6. Account preferences (forms for each email/preferences and changing pass/profile image)
  7. All their posts and listings (with up to 10 images each)
  8. The website has about 50 tables in the database. This page alone would likely take info from about 34-40 tables
  9. The page uses Ajax so most interactions will be done without page refreshes
  10. ...And some more

That doesn't look as much as I thought it to be but trust me, it's a lot. The page would probably consist of around 7000+ lines of code. Of course that includes the CSS and JavaScript, PHP, MySQL and html.

Should I go ahead with this, or would the page break for slower connections almost too often and be more of a nuisance?

One thing I could do is to only download the content of each tab when a user clicks on it, but if it's okay I'd like all the loading to be done when the user arrives on the page.

Hassle-free blogging platform that developers and teams love.
  • Docs by Hashnode
    New
  • Blogs
  • AI Markdown Editor
  • GraphQL APIs
  • Open source Starter-kit

© Hashnode 2024 — LinearBytes Inc.

Privacy PolicyTermsCode of Conduct