On a photography site every pixel of attention belongs to the photos, so anything added has to be small and quiet. Country flags and a visitor count give a gallery the sense of audience it otherwise lacks, and they do it in one line of text rather than a panel.
What you are trying to do here is show reach without putting anything in front of the images. Three widgets below do that; the other 15 in the set mostly do not, so they are not on this page. No app from the Wix App Market. Wix renders raw HTML and script tags inside an embed element, so there is nothing to install and nothing to pay for.
On Wix this goes in Settings → Custom Code, placed in Body – end — a ranked country list belongs at the bottom, where its lazy-loaded flags stay below the fold.
On Wix this goes in Settings → Custom Code, placed in Body – end — an all-time total is a footer artefact — nobody scrolls up to check it.
On Wix this goes in an Embed a Widget element on the page — a live count only changes behaviour when it sits in the same line of sight as the price or the button.
Footer only, at small size. Do not put a widget in a gallery grid or a lightbox — it breaks the one thing visitors came for.
For a single page, open the Wix Editor, click Add Elements → Embed Code → Embed HTML, paste the widget code into Enter Code, and resize the box to fit. For every page, go to your dashboard's Settings → Custom Code, add the code, choose All pages and place it at Body - end. Wix's help center notes that Custom Code requires a Premium plan with a connected domain; Embed HTML works on any Wix site.
Wix lets you arrange elements separately in the mobile editor. After adding an Embed HTML element, switch to mobile view and check the box isn't cropped or overlapping your images. You can resize it or hide it on mobile if it gets in the way.
Use Preview to check placement, then publish and test the live site, because embedded code runs fully only on the published site. Run PageSpeed Insights on the published page before and after adding the widget.
On a photography site the images are the product, so widgets have to be quiet. A small flag counter or visitor count gives the site a sense of audience without competing with the photos, and it reassures potential clients that your work is seen. Large panels, animated tickers and bright badges distract from the work.
Use the footer or a small corner of the about or contact page. Keep widgets off gallery pages entirely, or keep them below the last image. Choose a widget theme that matches your site's colors, usually dark or neutral, so it reads as part of the design.
Photography sites are already heavy because of images. Keep widgets to one or two, check that they load after your images, and test a gallery page in PageSpeed Insights before and after. If the score drops, move the widget to a lighter page such as about or contact.
Watch contact form inquiries and booking requests over a few weeks before and after. For a photographer, those inquiries are the real measure; visitor counts are only supporting evidence.
Only if they help clients trust you. A modest, quiet count or country flags can show your work is seen internationally. If your traffic is low, skip the counter and let testimonials and your portfolio speak instead.
Begin with a flag counter in the footer, styled to match your site's colors. Leave gallery pages clean. If you work with international clients, the flags quietly show your reach. Check inquiries over the next month, and remove the widget if it doesn't add anything clients notice. A quiet, honest signal of reach suits a portfolio far better than a loud one.
Every FeedPulse widget and badge is free to use with no signup: copy the embed code from the widget's page, paste it into your site and it starts working. There's no trial period and no card required. Some widgets that rely on outside data, such as weather or market prices, refresh on a schedule rather than every second, so they stay fast and free to run.
Give any new widget about four weeks before judging it. Compare the action that matters for your site, such as inquiries, bookings, sales or pages per visit, with the four weeks before you added it. Keep widgets that clearly help, move ones that might help in a better spot, and remove ones that made no difference. A page with fewer, useful widgets usually beats a page with many.
FeedPulse widgets show aggregate information such as visitor counts, countries and pages, not names or exact locations. Even so, mention any third-party widget in your privacy policy, and check whether your cookie notice needs updating for the tools you use.
Delete the block, section or embed element that contains the code and publish. Nothing else on your site depends on it. Your public FeedPulse stats page keeps the history it has already collected.
Start with one. A single widget in the right place is easier to judge, keeps the page fast and doesn't compete with your content. Once you've seen whether it helps, add a second only if it does a different job, for example pairing a visitor count with a countdown for a real offer. Avoid stacking several widgets that all say the same thing, such as two different visitor counters, because they make the page busier without adding information.
Widgets should never hide important information that isn't available elsewhere on the page. Keep your opening hours, prices and contact details as normal text, not only inside a widget. Check that widget colors have enough contrast against your background, and that the page still makes sense if a visitor's browser blocks third-party scripts. A widget should add to the page, not be the only place key information lives.
flag counter — On a photography site every pixel of attention belongs to the photos, so anything added has to be small and quiet. Country flags and a visitor count give a gallery the sense of audience it otherwise lacks, and they do it in one line of text rather than a panel.
Footer only, at small size. Do not put a widget in a gallery grid or a lightbox — it breaks the one thing visitors came for.
No app from the Wix App Market. Wix renders raw HTML and script tags inside an embed element, so there is nothing to install and nothing to pay for.