Our 38 pages are 253 phone screens tall, and the first link that can sell anything is either in the top tenth or the last eighth
I counted the links to our download page a while ago: 109 of them across Notifio's 38 pages, 76 of them the nav and footer repeated, and none at all in the five guides. Counting links tells you how many there are. It do
I counted the links to our download page a while ago: 109 of them across Notifio's 38 pages, 76 of them the nav and footer repeated, and none at all in the five guides.
Counting links tells you how many there are. It does not tell you where they are, and "where" is the only thing that matters on a page six screens long. So I loaded all 38 live pages at 390 by 844, the iPhone viewport, and measured the vertical position of everything.
253 screens
pages 38
total document height 213,900 px
253.4 phone screens
median page 6.69 screens
longest /terms 12.12 screens
shortest /download 2.90 screens
The shortest page on the site is the one whose entire job is to get an installer onto your machine, and the longest is the terms of service. That is probably the correct order.
The footer is the same 596 pixels on every one of the 38 pages:
footer, total 22,648 px 10.6% of every pixel on the site
footer, as a share of /download 24.4%
footer, as a share of /guides 19.4%
footer, as a share of /about 18.3%
footer, as a share of /terms 5.8%
footer text 9,158 characters 4.7% of the site's words
A quarter of the download page is the footer. It takes up 10.6 per cent of the site's pixels to carry 4.7 per cent of its words, which is what a fourteen-link sitemap column does when the page above it is short.
Two strategies, nothing in between
For each page I took the first link in the body content (ignoring the nav and footer) pointing at either /download or /pricing, and measured how far down the document it sits.
first CTA as % of page
/ 379 px 4.6%
/alerts/idealista 479 px 8.0%
/alerts/rightmove 517 px 8.4%
... 15 site pages, all between 8.0% and 9.6% ...
/alerts/facebook-marketplace 529 px 9.6%
-----------------------------------------------------------------
/download 1,704 px 69.6%
/guides 2,261 px 73.5%
/compare 3,897 px 82.7%
/guides/rental-documents-checklist 4,234 px 83.8%
... 13 guide, compare and audience pages, 83.8% to 87.8% ...
/for/students 5,877 px 87.8%
-----------------------------------------------------------------
/pricing /help /about /terms /privacy none
Sixteen pages put a conversion link in the top tenth of the document. Fifteen put the first one past 82 per cent. Two sit in between and five have none at all. For a site that was built page by page with no plan about this, that is a remarkably clean split, and it is not a coincidence: it is two templates.
The fifteen site pages are built from the alert-page template, which opens with an h1, a standfirst and a pair of buttons. You hit "Download" after 0.57 screens.
The guides, the comparison pages and the audience pages are built from one shared article layout, which is breadcrumb, h1, standfirst, sections, FAQ, and then a call to action at the bottom. On those pages the reader scrolls between 5.0 and 7.0 screens before the page offers them anything to click that leads to a purchase.
/for/students 6.96 screens before the first CTA
/compare/visualping 6.85
/guides/rental-scams 6.58
/alerts (the hub) 6.05
What is selling during those seven screens
One thing, and I measured it too. The nav is fixed top-0 and never leaves:
nav height 49 px
"Get Notifio" button 98 × 31 px = 3,038 px²
390 × 844 viewport 329,160 px²
share of the screen 0.92%
colour #737373 on #0a0a0a 4.18:1
font 13px, weight 600
For seven screens of a guide, the entire commercial surface of the website is 0.92 per cent of the viewport, drawn in grey at 4.18:1, which fails AA for 13 pixel text by a third of a point. The other two nav links, "Sites" and "Pricing", are the same colour at 29 pixels tall.
There is nothing wrong with the sticky nav as an idea. It is doing the job that the published 109-link count made look generous: 76 of those 109 links are this nav and this footer, and what the geometry shows is that on half the site they are not a supplement to an in-content CTA, they are the only one for several thousand pixels.
The scroll handler, since I was already in there
The nav restyles itself once, at 20 pixels of scroll:
const onScroll = () => setScrolled(window.scrollY > 20);
window.addEventListener("scroll", onScroll, { passive: true });
Passive, which is right. It also calls setScrolled on every single scroll event, which over a 3,600 pixel wheel fling is 30 calls, 29 of them setting the same boolean. React bails out of re-rendering when the next state is identical, so this costs 30 function calls and no renders, and the honest summary is that it is fine and that a scrollY > 20 check is not worth an IntersectionObserver.
What it buys is the nav going from flush and transparent to a floating rounded card: pt-3 px-4, max-w-6xl, rounded-2xl, a #262626 border, bg-[#0f0f0f]/90 and backdrop-blur-xl, over a 300 millisecond transition. Measured after scrolling, the nav sits at top: 12px with a 16 pixel radius and blur(24px). It is the one piece of motion on the site that fires on every page, and it is also what makes the CTA legible, because grey text on a blurred panel reads better than grey text over whatever happened to scroll past.
What I am changing
- A mid-article CTA in the shared layout. The geometry says exactly where: the first CTA should not be 87 per cent down a 7 screen page. After the second section is roughly two screens in, which on these pages is where the reader has decided whether they believe the article.
-
#a3a3a3for the nav links. 7.85:1 instead of 4.18:1 on the only control that is on screen all of the time. It is the same fix as the one I wrote up yesterday for the footer links that only reach readable contrast on hover, and the same two tokens. -
One link on
/help. It is 6.6 screens long, it is the page people land on when something is not working, and the body contains no link to either the download page or the pricing page.
All of it is measurable from a phone and a browser console: load any guide, run document.documentElement.scrollHeight / window.innerHeight, and then count how far you have to scroll before the page asks you for anything.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.