Create a resource budget and an optimization plan, then compare local page behavior without claiming an unmeasured performance score.
A fictional workshop page has a teaching resource budget: HTML 100 kB, images 800 kB and JavaScript 300 kB. A proposed revision keeps HTML at 100, reduces images to 240 and JavaScript to 120. These are scenario values, not measured network transfers from WikiFree.
| Resource | Before kB | Proposed kB |
|---|---|---|
| HTML | 100 | 100 |
| Images | 800 | 240 |
| JavaScript | 300 | 120 |
Specify the user task, device conditions and page state before measuring. A page can transfer few bytes yet block interaction with expensive script work. Separate laboratory tests from real-user field data. The case begins with a hypothetical byte budget so calculations stay distinct from browser observations.
Write a measurement plan and list the scenario assumptions.
Performance brief
Record your result and evidence here or in a separate file.
Hypothetical byte values are not labeled measured.
Add the test conditions beside every future measurement field.
The browser discovers and processes resources in an order affected by HTML, CSS and scripts. Identify resources needed for the first useful view and those that can wait. Avoid adding preload hints blindly; prioritizing everything defeats prioritization. Keep the core lesson text available without JavaScript.
Annotate the local fixture’s critical and deferred resources.
Loading map
Record your result and evidence here or in a separate file.
Each proposed deferral preserves the essential content.
Test the page with scripting unavailable before calling it resilient.
A budget makes regressions discussable. Calculate the proposed savings and identify which assets change. Optimize images with suitable dimensions and encoding, and remove unnecessary script work. The scenario does not justify a claim about Core Web Vitals or a particular PageSpeed score.
Calculate category savings and the total reduction.
Resource budget table
Record your result and evidence here or in a separate file.
Total changes from 1,200 to 460 kB, a 61.67% reduction.
Compute percentage savings against the original total.
Use the same browser conditions and repeat a test rather than selecting the best run. Record what actually happened, including cache state and viewport. The supplied local fixture lets you inspect resource and rendering behavior; it is not a clone of a live production page.
Record three local runs for the fixture and report the range, if the tools are available.
Measurement log
Record your result and evidence here or in a separate file.
No unperformed metric is filled with an estimate disguised as a result.
Leave unavailable measurements blank with a reason.
Prioritize changes by expected user benefit, effort and confidence. Separate measured bottlenecks from hypotheses and include a regression check. A performance change should not remove accessibility, content or necessary functionality. State what must be measured after a real deployment before claiming an improvement for users.
Write three actions and an acceptance check for each.
Performance handoff
Record your result and evidence here or in a separate file.
The plan includes a post-change comparison under the same conditions.
Replace guaranteed score claims with measurable acceptance criteria.
Deliver the measurement plan, loading map, budget calculation, actual local observations and prioritized actions. Explain one optimization that would be inappropriate for above-the-fold content.
Scenario estimates and measured browser results are clearly separated; no performance score is fabricated.
| Criterion | Points | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
The proposed total is 100 + 240 + 120 = 460 kB, compared with 1,200 kB. Savings are 740 kB or 61.67%. This is a resource-budget calculation, not a measured load-time or PageSpeed result.
This is a local performance exercise, not a live-site optimization or a guarantee of field metrics.