3 ms·
Unrelated to the actual content of the page.. but why does this site require 1.25Mb of javascript to load? It makes up nearly 70% of the entire page, and is re
by Twirrim 10y ago
Unrelated to the actual content of the page.. but why does this site require 1.25Mb of javascript to load? It makes up nearly 70% of the entire page, and is responsible for almost 60% of the requests needed to render the page. Do you really need to use that much javascript just to render a blog post. Why?
Those webfonts also took multiple seconds to retrieve leaving the page essentially completely blank to visitors until their browsers finally pulled them down. It paused long enough I was wondering if HN had sent sufficient traffic to bring the site down.
Here's an output to a quick stab at loading the page using pingdom: https://tools.pingdom.com/#!/cpZuGy/http://www.elcaminolegal.com/single-post/2016/10/04/Facebook-Reactjs-License https://tools.pingdom.com/#!/cpZuGy/http://www.elcaminolegal...
- talmand 10y agoBecause it's a basic site with a handful of pages with a blog that is built as a single page app. All the HTML of the page is generated by Javascript and dumped into the lone div inside the body. So, you take the big hit at first load but then it's snappy after that. Although, I would think the load size and speed for such a basic site would be better with standard HTML for everything but the blog. Also, the main JS file is 1690 lines long and even though it says it is min in the file name, it doesn't seem to be minified. The CSS file has some nice stuff going on in there. Some of the selectors are a bit long for my tastes though.