3 ms·
If you look at the source, you can see why it is slow. Tons of js linked in there, right in the <head>, no minification. They even embed jQuery twice on there (
by johnpolacek 13y ago
If you look at the source, you can see why it is slow. Tons of js linked in there, right in the <head>, no minification. They even embed jQuery twice on there (1.3.2 then later on 1.6.2). Also, lots of inline styles on the page. Looks like they are using a CMS, not sure which one though.
Nevertheless, that 3D rollover effect and infinite scroll in all directions is pretty fun.
- breck 13y ago> If you look at the source, you can see why it is slow. Good hunch, but not quite correct. To see why it is slow, you need to look at the Network Tab in your browser's debugger window. Their server is choking on requests.
- seriocomic 13y agoPartially correct, the number of requests (all that JS, CSS and images) without minification and compression enabled is making this not only twice the size (in Kb) that it needs to be, but the waterfall of blocked requests is terrible. See http://scans.zoompf.com/s/7180a12152cdf3dbd5087c2f7d09813d/report.html http://scans.zoompf.com/s/7180a12152cdf3dbd5087c2f7d09813d/r... for a cursory look at the optimization opportunities. I did LOL at the HTML comment near the end: <!-- JavaScript at the bottom for fast page loading -->