WebPageTest Pro Experiment Results

Experiment

ExperimentSettings: motog4v1024GVirginia USA
More
- First View only
- Test runs: 3
- Connectivity: 9000/9000 Kbps, 170ms Latency
- Custom Metrics
Experiment Info:
- Find/Replace Text
  
  This experiment will find and replace occurrences of text in the page, with the option of using regular expressions, capturing parentheses, and flags as well
  Assets/Instructions:
  <link[^>]*rel="preload"[^>]*>
  
  on
Related Links: Original (Control Run), Original Test
Share

Experiment Results

Experiments Applied:

Find/Replace Text
This experiment will find and replace occurrences of text in the page, with the option of using regular expressions, capturing parentheses, and flags as well
Assets/Instructions:
- <link[^>]*rel="preload"[^>]*>
- on
Experiment More

Links:

Experiment Impact (Notable changes between experiment and control)

Start Render	First Contentful Paint	Speed Index	Largest Contentful Paint	Cumulative Layout Shift	Total Blocking Time	Page Weight	Blocking Requests
5.7sFasterExperiment:4.5sControl:10.2s	5.72sFasterExperiment:4.43sControl:10.15s	6.05sFasterExperiment:5.27sControl:11.32s	5.84sFasterExperiment:5.82sControl:11.66s	0.332BetterExperiment:0.086Control:0.418	0.24sFasterExperiment:3.46sControl:3.7s	630KBLighterExperiment:2672KBControl:3302KB	4MoreExperiment:8Control:4

Remaining Opportunities

Here's how your overall opportunities look after this experiment:

Jump to Opportunities by Category:

Is it Quick? Needs Improvement.

This site was quick to connect and deliver initial code. It began rendering content with little delay. There were no render-blocking requests. The largest content rendered later than ideal.

Opportunities 8
Tips 8
Pro Experiments 8

Is it Usable? Needs Improvement.

This site had minor layout shifts. It took a long time to become interactive. It had 1 accessibility issues, none serious. Some HTML was generated after delivery, potentially delaying usability.

Opportunities 4
Tips 4
Pro Experiments 4

Is it Resilient? Not bad...

This site had no render-blocking 3rd party requests that could be a single point of failure. It had 3 security issues, 3 low-priority. Some HTML was generated after delivery, which can cause fragility.

Opportunities 2
Tips 2
Pro Experiments 4

Custom label	-l:<label>	220614_BiDcJE_T1-l:Original
Specific run	-r:<run>	220614_BiDcJE_T1-r:3
Repeat view	-c:1	220614_BiDcJE_T1-c:1
Specific step	-s:3	220614_BiDcJE_T1-s:3
Specific End Time	-e:<seconds>	220614_BiDcJE_T1-e:1.1

Experiment

Assets/Instructions: