Add a visit counter to your website and understand the totals
Install Tulo’s website counter widget, check domain settings and understand the difference between page views, unique visitors and live visitors.
Open Website Counter →Create and install your counter
Open Website Counter and give your counter a recognizable name, such as My portfolio. Set a website domain if you want the counter restricted to that site, then create it. Copy the generated embed snippet without changing its counter ID and paste it into your website’s HTML or a supported custom-HTML block.
Publish your page and open it in a normal browser. The widget displays the total recorded visits. If your website builder removes script tags, use its supported code-injection area; simply pasting the snippet into a plain-text editor will not run it.
Page views are not people
The total measures recorded page loads. The same person can generate several views by reloading or returning later, so ten views do not mean ten different people. It is not a live count of people currently on the page.
The widget records once per document load. Navigation in a single-page application may not load a new document, so do not expect every client-side screen change to count as another view. Browser blocking, network failures and automated requests can also affect the total; use it as a directional metric rather than a billing or audit record.
Use private analytics for context
You can create a counter without an account. Sign in to keep your counters in the dashboard and inspect private analytics, including daily views, devices, countries and referrers. Keep the guest browser session until signing in so its counters can move to your account.
Unique visitor estimates use a daily rotating identifier, not a permanent identity. They should not be interpreted as an exact count of distinct human beings across days. Compare trends over similar periods and check the source of unusual spikes.
When the widget is missing or the number looks wrong
Check that the published page contains the full snippet, the script can load and the counter’s domain setting matches the site. A restrictive Content Security Policy or an extension may block the script or its request. Review the browser console and network panel before changing the embed.
Testing repeatedly increases a page-load total, so use a separate counter for development. Domain restrictions prevent ordinary embeds on other sites, but they are not proof that every request came from a real person. Do not treat a counter as an anti-fraud system.