A reading progress bar that sits discreetly on every SharePoint page, an estimated read time shown up-front, and a visual cue when the reader reaches the end. Small UX polish that makes long pages feel shorter - and confirms to readers that yes, they've finished.
The Problem
Users open a policy page, a handbook section, a long announcement and immediately wonder "how long is this going to take?". No signal. No progress indicator. They scroll, lose their place, bounce out halfway through, and come back later wondering if they read it all. Long-form SharePoint pages feel like a commitment with no timer - so people skim or skip entirely.
The Solution
Page Read adds three tiny UX improvements that make a surprising difference: an estimated read time shown at the top of the page, a thin progress bar that fills as the reader scrolls, and a visible "read complete" indicator when they reach the end. Deployed once at tenant level, with rules to exclude page types where it doesn't belong.
How It Looks
Page Read changes state as the reader progresses. Minimal visual footprint, maximum feedback.
On Page Load
Estimated read time appears immediately. Readers know what they're committing to before they scroll.
While Scrolling
A thin bar tracks scroll depth as the reader works through the page. Subtle orientation that long pages normally lack.
At End of Page
A visible "Read" indicator confirms the reader has reached the end. Small detail that closes the loop on long-form content.
See It in Action
Screenshots coming soon. Page Read running on customer tenants.
One tenant-wide deployment, with precise control over where it shows.
Estimated Read Time
Calculated from the word count on each page. Shown near the top of the page so readers know the commitment before they start.
Scroll Progress Bar
A thin, unobtrusive bar that fills as the reader scrolls. Always-visible orientation without competing with content - the kind of polish long-form publishers have been using for years.
Read-Complete Indicator
When the reader reaches the end of the page, a visible "Read" state confirms it. Closes the loop on pages where "did I finish it?" is a genuine question.
Tenant-Wide Deployment
Page Read is an application customiser - installed once at tenant level, it appears on every SharePoint page automatically. No page-by-page setup.
Exclude by Page Type or URL
Hide the indicator on specific page types (homepages, bespoke landing pages) or URL patterns (executive microsites, short alert pages). Configure exclusions once at tenant level.
Theme-Aware and Responsive
Inherits your SharePoint theme for the progress-bar colour and text styling. Works on desktop, mobile and inside Teams tabs.
Included In
Web parts are sold as bundles, not individually. Page Read is one of the 13 web parts added in Complete, on top of the Starter 5.
Looking for the basics only? See the Starter Bundle →
Based on the word count of the page content. Uses a standard average reading speed (around 225 words per minute) by default, which is configurable at tenant level if your audience reads noticeably faster or slower. The estimate is a guide - prospects don't need it to be perfectly accurate, just honest.
Yes. Exclude by page type (homepages, landing pages, news articles, site pages) or by URL pattern (a specific site, a specific folder). Common exclusions: the intranet homepage where a progress bar would compete with the hero banner, executive microsites, short announcement pages.
No - Page Read is a UX enhancement, not an analytics tool. It shows the current reader their own progress. It doesn't record which users have read which pages, and it doesn't report back to admins. For compliance-style "X% of staff read the updated policy", you'd want a separate solution - we can help scope that as part of a retained support engagement.
Page Read is an application customiser - installed once at the tenant level, it runs on every modern SharePoint page automatically. No page-by-page edits, no site owners to chase. One deployment covers the whole intranet.
Negligibly. Page Read counts words on page load (one pass, very fast) and listens for scroll events throttled to avoid unnecessary work. It's a small JavaScript component that doesn't call any external services or APIs.
Book a 30-minute demo to see Page Read running on a real SharePoint tenant, or explore the Complete bundle.