Modern web browsers no longer treat every domain identically. In Google Chrome, an internal heuristic algorithm measures how actively and frequently you interact with individual websites, assigning each origin a dynamic score from 0 to 100 known as the Site Engagement Score.
While invisible during everyday browsing, your Site Engagement score profoundly influences browser behaviour. Chrome relies on this rating to decide whether websites can autoplay media with audio, deliver background synchronisation payloads, retain active processes in RAM without being frozen or discarded by Memory Saver, and prompt for progressive web app (PWA) installation. Understanding how to audit and adjust these ratings gives you granular insight into Chrome’s resource management.
How Chrome Calculates Site Engagement Scores
Chrome’s underlying Chromium engine calculates engagement metrics based on direct, authenticated user activity across five primary vectors:
| Interaction Vector | Points Awarded | Evaluation Threshold |
|---|---|---|
| Direct Navigation | 0.5 points per visit | Typing a URL, opening a bookmark, or clicking an external link to launch the origin. |
| Active User Input | 0.05 points per interaction | Keystrokes, mouse scrolls, and clicks registered while the tab is focused in the foreground. |
| Media Playback | 0.02 points per second | Listening to podcasts, streams, or watching videos with audible audio playback. |
| Foreground Dwell Time | Scaled continuous rate | Time spent actively viewing the page, capped per session to prevent infinite score inflation. |
| Daily Score Decay | Exponential reduction | If you cease visiting a domain, its accumulated engagement score steadily decays over time. |
How to Inspect Your Site Engagement Scores
You can inspect the live score table for every domain stored in your browser profile through a hidden internal Chromium page.
- Launch Google Chrome on your desktop (Windows, macOS, or Linux).
- In the address bar, type the following internal URL and press Enter:
chrome://site-engagement/ - Chrome displays a structured table detailing all tracked domains, their raw engagement score, and bonus factors.
You can click on the Score or Origin column headers to sort the table ascending or descending, immediately identifying which sites rank highest in your browsing history.
Threshold Levels and Browser Capabilities
Chromium categorises accumulated scores into discrete tiers that govern browser permissions:
- None (0): Newly visited or unvisited sites. Autoplay with audio is strictly blocked; background synchronisation and notification permissions are throttled.
- Minimal (> 0 to 1): Basic interaction established.
- Low (1 to 10): Established origin.
- Medium (10 to 50): Routine destination. Video streams gain autoplay privileges without manual click requirements.
- High (50 to 100): Core operational site (such as corporate webmail, project management dashboards, or messaging portals). Tabs are protected from aggressive tab-discarding by Memory Saver and receive priority background execution.
How to Manually Modify Site Engagement Scores
For web developers testing progressive web apps, autoplay policies, or background sync behaviour, Chrome allows you to manually override any origin’s engagement score directly from the interface:
- Open
chrome://site-engagement/in your browser. - Locate the target domain using the search function or by scrolling through the list.
- Click directly into the numeric Score input field next to the domain name.
- Enter your desired rating (for example, type
95to grant immediate high-tier privileges, or0to reset the site to a fresh baseline). - Press Enter to commit the new score.
Resetting and Clearing Engagement Metrics
If you want to wipe accumulated engagement metrics across all websites (for instance, to clear browser profiling or troubleshoot unexpected autoplay behaviour):
- Navigate to
chrome://settings/clearBrowserData. - Select the Advanced tab and choose All time as the time range.
- Tick Cookies and other site data along with Browsing history.
- Click Delete data.
Clearing site data purges the internal engagement database, restoring all origins to a score of zero.