How we count.

Visitors

MethodOne device on one day, counted without cookies: an anonymous key made from that day's random salt, the device's IP address and browser, and your site. The key changes at your site's midnight and the IP address is never stored, so someone who comes back tomorrow counts again. A period's visitors are the sum of its days.

Visits

MethodA visitor's pages with no gap of 30 minutes or more between them. A longer gap starts a new visit.

Pageviews

MethodEach page that loaded with the Wunderly script on it, and each move to a new page in an app that changes pages without reloading.

Phone, tablet, desktop

MethodBy the screen's width: a phone is under 600 pixels, a tablet 600 to 1,023, a desktop 1,024 and over. The script sends only which of the three, never the width.

On the site now

MethodVisitors with a page view in the last 5 minutes. Above 1,000 it shows 1,000+.

Source

MethodWhere a visitor's first page of the day came from, in this order: an ad (a link tagged with a paid utm_medium, such as cpc), the link's utm_source tag, the site that linked to you (search engines and social sites by name, any other by its address), or Direct when there was none of these. A Google ad without UTM tags counts as Google, because the script doesn't keep a link's other parameters. Each visitor counts under one source a day, so the sources add up to Visitors.

Rate

MethodOf a source's visitors, the share who reached out that day. Shown from 30 visitors; below that, a dash.

Reached out

MethodVisitors who sent a form (your Wunderly forms or any other form on your site, except a search box), or tapped your phone number or email address, that day. Each counts once a day, under the first of form, call or email in that order, so the three add up to the total. A form whose own script stops the send is still counted. Asking for directions isn't reaching out.

Taps on your phone number and email address

MethodVisitors who tapped a phone (tel:) or email (mailto:) link that day, once each a day, whatever else they did.

Directions

MethodVisitors who tapped a link to Google Maps, Apple Maps, Bing Maps, Waze or a map app that day. Counted and shown apart, but not as reaching out: asking the way doesn't mean they'll get in touch.

Then reached out

MethodVisitors who looked at the page and reached out afterwards the same day, counted from their first look at it. The share shows from 30 visitors.

Requests

MethodYour quote form and your contact form, sent in the period. Each send is one request, whether or not any pages were linked to it.

Quote requests

MethodYour quote form, sent in the period. Each send is one request.

Quote value

MethodThe estimates on those quote requests added up, each at the low end of its range, as our server computed it from their answers. A request without a number is counted in Quote requests and adds nothing here.

Priced at

MethodThe estimate our server computed from their saved answers; in a range, the low end. A dash means it couldn't be computed, so it isn't in any amount.

Looked at, in order

MethodWhen someone sends your form, the pages they looked at on your site that day, up to sending, and where the first came from. The form tells them it shares this. Without the script on the page, or with Do Not Track or Global Privacy Control on, nothing is attached.

Time on site

MethodFrom the first page they looked at that day to sending the form.

Opened

MethodYour form was on screen for a second, at least half of it visible or filling half the screen. Each browser counts once a form a day, days starting at your site's midnight, recognized by an anonymous key that changes at that midnight. "On /quote" names the pages of your site it was opened on most.

Sent

MethodAttempts that began in the period (someone answered a first question) and were sent, whenever they were sent. That's why it can differ by a request or two from Quote requests, which counts sends in the period.

Sent, of opened

MethodSent ÷ opened, from 5 opened. Below that we give the counts and no percentage.

Got past each question

MethodOf the attempts that began in the period, how many answered a question or went on past it. Opened is everyone who saw the form; Sent is those who sent it. Attempts we delete 30 days after they stop (their answers go) still count here by the question they stopped at, which is all we keep, with the low end of the estimate they were shown, if any (for What we noticed). Someone who deletes their answers leaves every count.

Stopped here

MethodThe drop from the step before: who got that far and no further. At the first question it includes everyone who opened the form and never answered. The share of those who opened shows from 5 opened.

Where the most people stopped

MethodThe question with the biggest drop, the earlier one on a tie. We name it once 5 people in all have stopped, and say whether it comes before the estimate.

At most five, chosen by the same rules every time: insights about reaching out first, then traffic that doesn't reach out, then traffic, and within each the largest difference. Below its minimum a rule says nothing. No AI writes any of it.

Page lift

SaysVisitors who looked at your Gallery were almost 4 times as likely to reach out.

CountedFor each page: its visitors who reached out at or after their first view of it that day, against the day's other visitors who reached out without viewing it. Each visitor is one device on one day. Pages one of your forms was opened on are left out, since people reach out there.

Shown from30 visitors who viewed the page, 30 who didn't, and 5 of its visitors who reached out afterwards.

Shown whenIts visitors were at least 1.5 times as likely to reach out. When several pages qualify, the one with the biggest difference.

Best source for requests

SaysGoogle brought 9 of your 12 quote requests, worth about $13,900.

CountedYour quote form's requests sent in the period, each under the source of the visit it was sent on. A request with no linked visit counts in the total and under no source. Value is the sum of each estimate's low end, rounded down to the hundred.

Shown from5 quote requests.

Shown whenOne source brought more than any other, at least 2 requests and at least a third of them.

Form stop

SaysMost people who stopped in your quote form left at “How big is the deck?”.

CountedYour quote form, question by question, over the attempts started in the period: someone who opened the form and didn't send it stopped at the first question after the last one they answered (the first question, if they answered none).

Shown from20 people who opened the quote form.

Shown whenMore than half of the people who stopped did so at the same question, or just before sending.

Price threshold

SaysAbove an estimate of $8,000, most people didn't send their quote request.

CountedYour quote form's attempts started in the period that were shown an estimate, each at its last estimate's low end, split at a round amount: how many on each side sent it. The amounts tried are the estimates shown, each rounded down to two figures.

Shown from10 people shown an estimate on each side of the amount.

Shown whenUnder half sent above the amount, at most half the share that sent below it. When several amounts qualify, the one with the biggest difference, then the lower.

Slow page that loses people

SaysYour Services page takes 6.1 seconds to load on phones, and 7 in 10 phone visitors leave it.

CountedThe page's load time on a phone (LCP) from the latest weekly check, against its phone visits in the period: visits that started on the page, and of those, the ones that saw no other page.

Shown from30 phone visits that started on the page.

Shown whenIt loads in more than 4.0 seconds on a phone, and more than half of those visits ended there. When several qualify, the one that loses the largest share.

Hidden from Google

SaysYour Gallery page tells Google not to list it, and it's one of your best pages for reaching out.

CountedA page the weekly check found set to noindex (in its meta robots tag or its X-Robots-Tag header), against the pages ranked by visitors who reached out at or after viewing them in the period.

Shown fromThe page has reach-out data: at least 1 visitor who reached out after viewing it.

Shown whenIt's one of your 5 best pages for reaching out. When several qualify, the best of them.

Form accessibility

SaysA question in the form on your Contact page has no label a screen reader can announce.

Countedaxe-core's automated checks in the weekly check, on the home page, up to 2 pages with a form and the 2 most-visited pages: the rules that find a field without a name (label, select-name, aria-input-field-name, aria-toggle-field-name, input-button-name). Automated checks catch some accessibility problems, not all.

Shown fromAny field the check finds.

Shown whenThe check found one. When several pages have one, the one with the most visitors in the period.

Weak source

SaysYour Facebook ads brought 304 visitors but only 2 reached out. Most saw one page.

CountedEach visitor's day under the source of their first page that day: how many reached out that day, and how many viewed one page in all, against everyone who looked at a page on the site that day. Direct is left out.

Shown from100 visitors from the source.

Shown whenIts visitors reached out at most half as often as the site's, and more than half of them viewed one page. When several qualify, the one furthest below the site.

Broken link on a busy page

SaysA link on your Gallery page is broken, and it's one of your 10 busiest pages.

CountedA link to another page of your site that failed in the weekly check (an error, or no answer) and again when asked a day later, on a page ranked by its visitors in the period.

Shown fromThe page is one of your 10 pages with the most visitors.

Shown whenA broken link is on it. When several pages have one, the busiest.

Search snippet missing

SaysYour Railings page has no description for search results.

CountedA page the weekly check read with no <title> or no meta description (or only spaces), among pages search engines may list: it loaded, isn't set to noindex and doesn't point elsewhere as canonical.

Shown fromThe page had at least 1 visitor in the period.

Shown whenIts title or description is missing. When several pages qualify, the one with the most visitors.

Traffic change

SaysVisitors were up 25% on the 30 days before.

CountedThe period's visitors against the period before it, of the same length and cut at the same time of day, as the summary's change. Each visitor is one device on one day.

Shown from50 visitors in each period, and a whole earlier period.

Shown whenUp or down at least 20%.

New source

SaysNew in the last 30 days: 304 visitors from Facebook ads.

CountedEach visitor's day under the source of their first page that day, against the period before it, of the same length. Direct is left out.

Shown from10 visitors from the source, and a whole earlier period.

Shown whenNo visitor came from it the period before. When several qualify, the one with the most visitors.

Once a week, and once soon after you install the script, WunderlyBot reads your site and looks for what keeps people from finding it or using it. Each finding stays on your fix list until a later check no longer sees it, or you dismiss it. Automated checks catch some accessibility problems, not all.

What the check reads

ReadsYour robots.txt and sitemap, then up to 250 pages, starting from your home page, your 20 most-visited pages and the pages your forms were opened on, and following links to your own site. Links and images are asked whether they answer, not downloaded.

NeverIt sends nothing: GET and HEAD requests only, and no form is ever sent. It asks for one page, link or image a second at most; a page opened in a browser loads its own files as any browser would. It obeys robots.txt under the name WunderlyBot.

WhenAbout once a week, at a time set for your site, and once within an hour of your first visit.

In a browserA page with almost no text (under 200 characters) is opened in a browser once, at most 20 a check, so links drawn with scripts are found.

Hidden from search

NoindexA page that tells search engines not to list it (a robots meta tag or an X-Robots-Tag header saying noindex or none), shown only when it had a visitor in the last 30 days.

Robots.txtYour robots.txt keeps every search engine out of the whole site.

SitemapNo sitemap in robots.txt, at /sitemap.xml or at /sitemap_index.xml; or a sitemap that leaves out one of your 10 most-visited pages. A sitemap over 500 addresses isn't judged.

Titles and descriptions

MissingA page search engines may list (it loaded, isn't noindex, and doesn't name another page as its canonical) with no <title>, or no meta description, or only spaces.

The sameTwo or more such pages with the same title, or the same description, ignoring case and spacing. Pages with a query string or a redirect aren't compared.

Broken links and images

BrokenA link to your own site, or an image on any site, that answers with an error or not at all. A site that turns the bot away (a challenge, or too many requests) doesn't count as broken.

Asked twiceA failure is asked again a day later, and shown only if it fails again. It leaves the list when a later check finds it working, or no longer finds the link.

Large images and insecure files

LargeAn image over 500 KB, by the size the server reports, or by reading it when it doesn't say.

Alt textAn image with no alt attribute. An empty alt (alt="") is fine: it marks a decoration.

InsecureA file loaded over http: on a page served over https:, which browsers may block.

Speed on phones

MeasuredOn your home page and your 2 most-visited pages, in a browser set up as a phone (a 412 by 915 screen, the processor slowed 4 times), waiting for the page to load and 3 seconds more.

SlowLoad time (largest contentful paint) over 4.0 seconds, time blocked by scripts over 0.6 seconds, or layout shift over 0.25: Google's lines for "poor". Times round down to a tenth of a second.

A caveatThe network isn't slowed, so a phone on a weak connection can be slower than the time shown. We'd rather say too little than too much.

Accessibility

Checkedaxe-core's automated rules for WCAG 2.0 and 2.1, levels A and AA (wcag2a, wcag2aa, wcag21a, wcag21aa), on your home page, up to 2 pages with a form and your 2 most-visited pages. Only problems axe rates serious or critical are shown.

Not checkedAutomated checks catch some accessibility problems, not all. Nothing here says a site meets a law or a standard.

Phone visits that ended there

CountedVisits from a phone whose first page was this one, and of those, the visits that saw no other page. Each visit is one device on one day; a reload of the same page stays one page.

Used byThe note about a slow page that loses people.

The period

MethodToday, or the last 7 days, 30 days or 12 months, each ending now, with days starting at your site's midnight. 12 months is 52 weeks (364 days), so the chart's weekly bars are whole weeks. The 12 months before count their last day whole, because hour-by-hour records are kept 90 days.

Up or down

MethodAgainst the period before it, of the same length: the 30 days before for 30 days, yesterday up to this time for Today. It's a percentage once the earlier period has at least 50; below that we give the earlier count. Until your site has a whole earlier period, we don't compare.

The weekly report's week

MethodThe 7 whole days before the day the report goes out, with days starting at your site's midnight: your main page's 7 days, read at the very end of the day before. It's compared with the 7 days before those.

Small numbers

MethodA rate needs 30 visitors behind it, and a change needs 50 in the earlier period to be a percentage. Below that we give counts, or say there aren't enough visits yet to compare.

Pageviews for billing

MethodA site's pageviews, counted as Pageviews are, in its calendar month, with the month starting at the site's midnight on the 1st. Only days since the site joined your bill count. The running figure is as of the last hourly count. Each site includes 100,000 a month; above that, each 100,000 or part of it is $10, added after the month ends. A trial is never charged.