Codeinwp / Codeinwp/otter-blocks

To load in footer or not to load

Open
#1,076 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

performance
Dominant language
JavaScript
Stars
198
Forks
36
Avg merge
3d 4h
Merged PRs (30d)
30

Description

Description:

Of course, the title is a reference to Shakespeare, but the rest of the issue refers to testing how much CSS we should load in the Footer for it to start giving us negative performance.

Currently:

  • All the CSS bundled with the plugin loads in the header.
  • All the generated CSS is loaded in the footer.

We can test and see if it's the about of CSS or the type of CSS that affects the performance, or if it's how much we load inline or from a file.

Alternatives:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin by identifying where the plugin bundles CSS for the header and generates CSS for the footer; no specific files or tests are named in the issue. Measure whether CSS amount, CSS type, inline loading, or file loading causes negative performance, then document a supported loading strategy based on those comparisons.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, javascript
Domain
frontend, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.