4 ms·
They need to improve the suggestions: > Reduce the amount of <iframe> tags. There are 1 iframe elements on the page. 1 iframe isn't bad. This shouldn't even b
by chime 16y ago
They need to improve the suggestions:
> Reduce the amount of <iframe> tags. There are 1 iframe elements on the page.
1 iframe isn't bad. This shouldn't even be worthy of a tip.
> Reduce the amount of tags that use the style attribute, replacing it with external CSS definitions. There are 1 nodes that use the style attribute.
1 style isn't bad either. They use it on their own page.
> Found 116 <script> tags on page. Try to reduce the amount of script tags.
This shouldn't be just a normal warn. 100+ script tags should be a major warning.
> Nesting depth is very high. Some of the nodes are nested more than 15 levels deep (these are marked with a dashed red border).
> Nesting depth is a little high. Reducing it might increase performance.
Both of these are shown on HN. Only one should be shown.
> Some nodes use transparency. To improve rendering performance, try not to use the CSS opacity property (found 2 nodes, marked with a dashed blue border).
It would be awesome if it could highlight these nodes somehow. Actually, would be awesome if it could highlight all visibile nodes that match any warning/tip. They already do that with nodes at 15+ nesting depth.
- gruseom 16y agoReduce the amount of tags that use the style attribute, replacing it with external CSS definitions. Is this supposed to be for performance or are they just suggesting "good practices"? If it's performance, I'd like to see some evidence that style attributes slow down the DOM. I don't know of any, and it would be significant.
- btipling 16y ago>This shouldn't be just a normal warn. 100+ script tags should be a major warning. How do you think JSONP works? Why is this bad?
- kwamenum86 16y agoThe bookmarklet might assume they were there on initial load.
- madrobby 16y agoYou're welcome to fork & change - we'll gladly merge good suggestions in!