Portfolios get judged in seconds and most visits are a hiring manager or client checking whether you are a real, active practitioner. A visitor globe showing international traffic and a page-speed badge proving you build fast sites both say 'competent' without a paragraph of claims.
What you are trying to do here is turn a visit into an enquiry while the work is still on screen. 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 an Embed a Widget element on the page — it's the most visual widget you have, so it earns a spot in the content rather than the chrome.
On Wix this goes in Settings → Custom Code, placed in the Head — one paste in the head gives every page its own score — the badge auto-detects which page it's on.
On Wix this goes in an Embed a Widget element on the page — it's social proof for a specific project, so it goes inline next to what it's vouching for.
Keep these near the bottom of the home page or on your about page — never above the work itself. The GitHub stars badge belongs beside the project it refers to.
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.
A portfolio exists to get you hired or commissioned, and most visitors are a client or hiring manager deciding in a minute or two whether to get in touch. Widgets help only when they back up that you're active and capable: a page-speed badge on a developer's or designer's site, a GitHub stars badge beside an open-source project, or a visitor globe on the about page. Anything that pulls attention away from the work itself costs you.
The work goes first, always. Put the visitor globe or a visitor count on the about page or at the bottom of the home page, the page-speed badge in the footer, and each GitHub stars badge directly beside the project it measures. Keep the contact button visible on every page, and check on a phone that no widget pushes it down or covers it.
Choose widgets that prove something relevant to the job you want. A web developer showing a good mobile speed score is demonstrating the skill being hired for. A designer showing a GitHub badge is not. If a badge shows a weak number, such as a slow speed score or a project with very few stars, leave it off until the number helps you.
For a portfolio the only number that matters is enquiries: contact form submissions, emails and booking calls. Note how many you get in the month before adding a widget and the month after. If nothing changes, the widget isn't hurting you, but it isn't helping either, and a cleaner page may be better.
Only if the number helps. A designer with clients in several countries can use a visitor globe to show reach without saying a word. A brand-new portfolio with a handful of visits a week is better off without a public counter; let your case studies and testimonials do the work until traffic builds.
If you build websites, start with the page-speed badge in your footer, because it shows the skill clients are paying for. If you publish open-source work, add a GitHub stars badge next to that project. Add a visitor globe on the about page once you have steady traffic from more than one country. Review enquiries after a month and remove anything clients never mention.
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.
visitor globe widget — Portfolios get judged in seconds and most visits are a hiring manager or client checking whether you are a real, active practitioner. A visitor globe showing international traffic and a page-speed badge proving you build fast sites both say 'competent' without a paragraph of claims.
Keep these near the bottom of the home page or on your about page — never above the work itself. The GitHub stars badge belongs beside the project it refers to.
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.