Install a counter without shifting the layout

A counter arriving after the text can move nearby content if the page has not reserved space for it. The installation should preserve the generated dimensions, fit the container and avoid delaying measurement unintentionally. These are separate checks: a stable layout does not prove that every page view was counted.

Keep the generated dimensions

Choose the design in Stats4U and copy its installation code. For an image counter, keep its width and height when the generated code includes them. These dimensions describe the image’s aspect ratio and let the browser reserve space before the image arrives. Do not copy dimensions from another design.

If an older image snippet has no dimensions, read the selected image’s natural width and height in the browser or its design information. Add those actual values. Numbers chosen only to make the box fit can distort the image.

<img src="COUNTER_IMAGE_URL" width="ACTUAL_WIDTH" height="ACTUAL_HEIGHT" alt="Visitor statistics">

This is a template, not installation code: replace the uppercase placeholders with the generated image address and measured dimensions. Use a short, meaningful alternative text when the image conveys information; an empty alternative is suitable only when equivalent information is already available and the image is decorative.

Fit the container without hiding the problem

A narrow sidebar can be smaller than the selected counter. Choose a smaller design or put the counter in a wider section. A responsive image rule can preserve proportions, but a stretched preview is not a substitute for checking whether its text remains readable.

1. Load the page with a slow connection and watch the content around the counter.
2. Inspect the result at 320 and 360 CSS pixels. Check the page itself for sideways movement.
3. Temporarily block the image request in browser developer tools. The reserved space and surrounding links should still behave sensibly.

Do not postpone the counting request by accident

For an image counter, lazy loading postpones the image request until it approaches the viewport. When that request is what counts a visit, visitors who never scroll near a footer may be missed. Do not add loading="lazy" to a counting image as a general performance fix.

The generated asynchronous JavaScript integration separates tracking from a simple image-only installation and is required for additional events. Preserve the generated integration instead of combining several snippets for the same counter. If layout is stable but totals remain unexpected, check placement and tracker requests separately.

Next step

Use the installation guide that matches the website platform.

Open the installation guide

MDN: <img> — width, height, alt, loading