wurmlab / wurmlab/wurmlab.github.io
Loading javascript and css and font before real content
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 7
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
THis is a bad thing says analytics:
Optimization Suggestions
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 4 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Optimize CSS Delivery of the following:https://maxcdn.bootstrapcdn.com/…ootswatch/3.3.6/flatly/bootstrap.min.css https://fonts.googleapis.com/css?family=Lato:400,700,400italic https://netdna.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.css https://wurmlab.github.io/css/custom.css
Furthermore, we should put a browser cache date on images and css (not on content) - currently everything that is more than 10minutes old gets redownloaded
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the analytics findings for the wurmlab.github.io page and inspect the referenced resources: Bootstrap, Google Fonts, Font Awesome, and css/custom.css. Check how static assets are loaded and cached, then verify that above-the-fold content renders without the reported blocking resources and that static CSS and images receive longer browser-cache lifetimes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bootstrap, css, html
- Domain
- performance, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100