ampproject / ampproject/amphtml
Reduce the impact of third-party code
- Dominant language
- JavaScript
- Stars
- 14.9k
- Forks
- 4.1k
- PR merge metrics
- No merged PRs in 30d
Description
### Description
When AMP Scripts Imported into page google page speed insights give performance optimisation for AMP scripts as below
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading.
### Reproduction Steps
Check AMP website with google page speed insights
### Relevant Logs
_No response_
### Browser(s) Affected
Chrome
### OS(s) Affected
_No response_
### Device(s) Affected
_No response_
### AMP Version Affected
_No response_
Contributor guide
Research direction
Start by reproducing the report on the AMP website with Google PageSpeed Insights in Chrome, focusing on the AMP Scripts warning. Determine which third-party providers or scripts are responsible and define a measurable performance target; the issue currently names no files, tests, or specific change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100