8 ms·
> But on the same subject all pages would be data heavy. Not all of them. For a trivial example, an in-depth article about a topic would be penalized more than
by StavrosK 9y ago
> But on the same subject all pages would be data heavy.
Not all of them. For a trivial example, an in-depth article about a topic would be penalized more than a more epidermic one, because it would contain more text, graphs, etc.
> For reference, I optimized my website a while ago and ended up with the average page being < 15K.
I feel you, I absolutely hate that my website uses a bunch of stuff for almost no reason. 80 KB of CSS or 90 KB of font isn't awesome, and I started a project to provide information on how to create lighter websites (https://www.lightentheweb.com/ https://www.lightentheweb.com/, stalled a bit).
All I'm saying here, though, is that the solution is more nuanced than "heavier = lower". AMP is definitely not a step in the right direction, though. I wonder if Google could give sites that used a specific CSS file and no JS a bump, rather than loading things on their own domain.
- jacquesm 9y ago> For a trivial example, an in-depth article about a topic would be penalized more than a more epidermic one, because it would contain more text, graphs, etc. But such trivial examples should be trivial to get right no? It's all about the relative weight of the various factors that determine the ranking and a 'lightweight' article could be recognized as such.
- StavrosK 9y agoWell, that's my point, it's not trivial to automatically recognize which photos are content and which are style. You want to have many content photos, but having many style photos probably means cruft. How do you recognize which is which?
- jacquesm 9y agoHow does AMP recognize this right now?
- StavrosK 9y agoIt doesn't, it just forces you to display the pages through Google, stripping everything else, which is much easier to implement than recognizing if a web page's heft is because of legitimate content or ads.
- jacquesm 9y agoSo what difference would it make? After all, this is the result after AMP has done all its cleaning, which would give you a pretty accurate measure for page weight. What remains is the actual content of the page. It's the cruft that should be penalized, not the actual content.
- dmitriid 9y agoAMP doesn't do the cleaning. You as the publisher/author have to implement an AMP page yourself and then alert Google of its existence.
- StavrosK 9y agoExactly what my sibling comment said, it's the publisher (presumably a human) who does the cleaning. It's not as easy to get a bot to clean things up and then measure weight, and the various "Readability" views aren't always correct (they're using heuristics). Sounds like a publisher-assisted "readability view" would solve both problems, though. It would allow the user to view a "lighter" version of the page and search engines could just measure how large the "non-light" version is and penalize accordingly. I'm afraid that would incentivize the publisher to put ads and other crap in the "light" view, though.
- WA 9y agoSame way almost all browsers offer a Reading view. They still show the article image. Doesn't seem to be that hard of a problem.