Hotjar website examples and behavioral-research planning (20 Real-World Examples)
Twenty public properties with verified Hotjar source references, genuine screenshots and practical questions for studying real visitor tasks.
A useful behavioral study begins with a question, not a collection of clicks. These examples show search, product discovery, service finding and editorial exploration as distinct situations to investigate.
Hotjar’s official learning material describes installing a tracking code and then verifying the installation. That distinction matters: finding an initializer in a public response is not the same as proving it executed or observing what an account records. This collection identifies dated code references and reviews the visible public interface, without claiming access to anyone’s sessions or analytics results.
The examples range from university and developer documentation to retail, travel and local services. They offer concrete research questions: can someone distinguish support from shopping, find the right documentation route, or understand a campaign destination? Those questions are more useful than guessing intent from a screenshot or assuming that every additional click indicates frustration.
Before the examples
What makes good Hotjar website development in 2026?
Start with a bounded research question
Name the task, audience and decision the study should inform. A returning customer and a first-time visitor may reasonably take different paths. Write down what would count as evidence before inspecting a recording or heatmap, and corroborate ambiguous behavior rather than assigning intent automatically.
Confirm the actual authorized setup before relying on data. Hotjar’s own material treats installation verification as a distinct step. A script reference, CSP allowlist or preconnect cannot prove that collection is active, complete or configured appropriately for the pages being studied.
Identify sensitive routes, inputs and content that should not enter research tooling. Document consent requirements, suppression decisions and who reviews the setup. Do not use a competitor’s public script reference as evidence that its privacy choices are appropriate for your own site.
Russell Hobbs Germany, the University of Chicago, Docker documentation, Datadog documentation and Paula’s Choice lead this collection. These are specific public properties with initializer or loader-reference evidence, not claims about every service operated by their organizations.
We start with five recognizable brands or organizations: Russell Hobbs Germany, University of Chicago, Docker documentation, Datadog documentation, Paula’s Choice. Each attribution applies to the named website property, not every product or website belonging to its organization. This is a curated reading sequence, not a measured ranking.
Russell Hobbs Germany places a pastel appliance collection in a split promotional panel, with a simple headline and a compact discovery action. Below, red controls distinguish registration, offers and recipes. The practical ownership links provide a counterweight to the product campaign and make this more informative than a homepage devoted entirely to shopping.
What you can learn
A useful behavioral-research question is whether visitors recognize the ownership routes without entering the promotion. Study a defined task with an appropriate consent and suppression plan, not an assumption that every visit should become a sale. Keep regional language and support intent separate when interpreting results. Include a support-seeking participant in the study, since successful registration may be unrelated to interest in the featured appliances.
Pros
Product colors and campaign typography share a calm visual palette.
Registration and recipes are offered as distinct practical routes.
Cons & considerations
Carousel artwork can change what is visible before a visitor acts.
An ownership task may have a different success definition from shopping.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
The University of Chicago presents a research photograph with a large white headline and a compact maroon navigation frame. Its public information and institutional menus remain above the image rather than inside it. This offers a concrete research contrast between visitors drawn into a current story and those arriving with an already defined university task.
What you can learn
Form a research question around audience routing before observing clicks. A prospective student, staff member and general reader may all ignore the hero for good reasons. The cached page contains a Hotjar initializer reference; that does not establish execution, recording, visitor consent or any particular analytics result. Keep institutional audience assumptions explicit in the brief, and corroborate any observed hesitation with a direct question rather than a guess.
Pros
A single large photograph gives the feature an identifiable subject.
Permanent navigation stays outside the editorial image treatment.
Cons & considerations
The headline competes with a visually busy research scene.
One homepage observation cannot explain the needs of every university audience.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Docker's documentation page uses a large central search prompt above four evenly spaced destination cards. Its blue navigation bar carries the brand without consuming much vertical space. The mostly white surface makes the difference between asking a specific question and choosing a guided starting point easy to see in the captured layout.
What you can learn
Investigate whether newcomers and returning developers choose different entrances. Pair behavioral observations with a bounded task and a clear definition of a useful result. Suppress search content where appropriate: technical questions may contain proprietary identifiers, and a public tracking reference says nothing about the actual collection settings. Record whether the intended answer is reached, not merely whether the search field receives a click during the task.
Pros
Four destination cards offer an alternative to entering a query.
The central search area is visually separated from global navigation.
Cons & considerations
Open-ended search needs useful failure and empty-result handling.
A sparse first screen does not prove that deeper documentation is findable.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Datadog's documentation hub places search inside a purple branded panel and follows it with update cards and topic groups. The layout balances a direct question with browsing across a large product surface. A narrow corporate header remains distinct from the documentation body, which helps distinguish product marketing from the material a developer came to use.
What you can learn
Frame an observation around a specific documentation question rather than total clicks. Compare search-led and category-led paths without collecting customer configuration values or pasted secrets. Public source establishes a Hotjar script reference in the sampled property, not a claim about the monitoring of authenticated customer applications. Assess terminology with realistic questions from different product areas, since identical click paths can conceal very different levels of understanding.
Pros
Search has a strong visual position above the topic categories.
Grouped links acknowledge that the documentation covers different product areas.
Cons & considerations
Product breadth can make similarly named routes difficult to distinguish.
Research must exclude private configuration details from captured inputs.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Paula's Choice presents a bright gift-kit campaign beneath a plain shopping and skincare navigation. Product packaging occupies the right side, while a circular pink panel holds the offer and action. The interface gives a visitor both a seasonal invitation and a more deliberate route through categories or concerns. Those are different tasks worth studying separately.
What you can learn
Test whether visitors seeking a particular product concern can avoid the gift campaign easily. Interpret browsing paths in the context of the task rather than assuming more clicks are better. The cached source contains Hotjar configuration, but it does not establish active recording or the treatment of sensitive skin-related inputs. Keep the research hypothesis tied to a specific navigation label, then check comprehension rather than judging success from visual attention alone.
Pros
The gift action sits within the same visual unit as the offer.
The header supplies product-research paths independent of the campaign.
Cons & considerations
The large circular message dominates quieter navigation choices.
Personalization fields need explicit research and privacy boundaries.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
First Bus places a white journey-planning form across the bottom of a purple campaign panel. The featured announcement uses a poppy photograph, while the header separately exposes region selection, tickets and support. An app update appears below. The page therefore mixes immediate journey intent with information that matters at a different point in the customer relationship.
What you can learn
Ask whether the announcement obscures or supports route planning for the chosen task. Examine field comprehension with controlled inputs rather than real travel histories. A Hotjar reference identifies a sampled script association, not evidence that trip details are recorded, consent is valid or users successfully obtain tickets. Include a task that begins with an unfamiliar region, and verify that the participant understands which service area is currently selected.
Pros
Planning fields remain visible within the opening campaign area.
Region selection is separated from the general promotional message.
Cons & considerations
Campaign imagery competes with a time-sensitive practical task.
Location and journey details require careful suppression in research tooling.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Hilton & Hyland opens with a monochrome architectural detail and a small central statement about the brokerage. The dark navigation frame is deliberately restrained, allowing the photograph to dominate. This is a useful reference for studying whether an atmospheric introduction leads visitors toward property information or leaves them searching for the first practical action.
What you can learn
Choose a task such as finding a property category, then observe the route without assuming the cinematic treatment helps or harms it. Separate aesthetic preference from navigational evidence. A public Hotjar initializer does not reveal recording configuration, lead quality or the outcomes of private inquiries. Ask participants what they expect the next destination to contain before treating their choice as evidence of a successful property journey.
Pros
The restrained monochrome treatment creates a coherent visual identity.
Navigation remains distinct from the full-width image.
Cons & considerations
Small text over photography may be hard to discover quickly.
A brand-led opening delays concrete property information for task-focused visitors.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Apartamento places a large outdoor portrait scene beneath a simple magazine header. A small centered title and video action sit over the image, while shop, membership and stories remain in the top navigation. The composition reflects an editorial-first identity, but the permanent menu makes clear that the property supports several different kinds of visits.
What you can learn
Separate watching a feature, reading a story and finding a product when defining a study. A visitor who skips the video may still complete the intended task. Public Hotjar references establish a sampled resource association only; they do not reveal recordings, engagement duration or consent choices made by actual readers. Check whether the participant can return to the magazine after opening a feature without losing the context of the original task.
Pros
The minimal menu identifies the publication's different activities.
A single large feature avoids an overcrowded opening grid.
Cons & considerations
Small overlaid controls need strong contrast and keyboard treatment.
Video-centered presentation may postpone text-based discovery routes.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Chronicle Books uses a bright blue gift campaign with a small cluster of covers on the right and a clear shopping button on the left. The header keeps categories and search above the promotion. The photographed objects give a visual hint of the catalog while the campaign headline offers a broader seasonal route.
What you can learn
Study whether visitors with a known title use search successfully and whether gift shoppers understand the campaign destination. These questions need different tasks and interpretations. A script reference does not establish the contents of recordings, the effectiveness of the offer or the behavior of a later checkout. Compare the labels people use for gifts with the categories offered by the catalog before proposing a different campaign hierarchy.
Pros
Covers provide specific product context within the gift campaign.
Search remains available outside the promotional artwork.
Cons & considerations
Seasonal messaging can overshadow less gift-oriented catalog needs.
A large campaign image gives limited evidence about deeper product filtering.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Landyachtz leads with a skateboarder in motion and large expressive lettering near the bottom of the photograph. Its white header is comparatively quiet, separating skate, bike and apparel routes. The page makes the activity feel immediate, while leaving the question of how quickly a visitor finds a suitable product to the surrounding navigation.
What you can learn
Use a task that specifies the intended product or skill level before interpreting an interaction trail. Watching a compelling photograph is not equivalent to understanding a catalog. The public Hotjar initializer supports a scoped technology association, not a conclusion about recorded sessions, purchase intent or customer satisfaction. Include a beginner task and an experienced shopper task so familiarity with specialist vocabulary does not distort the interpretation.
Pros
Activity photography establishes the product context immediately.
Product families remain separated in a simple header.
Cons & considerations
Decorative lettering can be harder to read over complex imagery.
The hero alone does not explain suitability or equipment differences.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Montane places a close view of insulated clothing behind a winter-readiness headline. Two shop actions sit beneath the title, and large category tiles begin immediately below. The dark header and promotional strip frame the photograph without matching its visual complexity. It is a useful reference for the boundary between an evocative seasonal story and direct catalog access.
What you can learn
Compare a visitor seeking a known garment with one exploring seasonal options. Define success around finding suitable information, not merely reaching a campaign page. The Hotjar source reference is dated evidence of an integration surface, not proof that any particular user session or buying decision was observed. Observe whether the category labels answer the chosen shopping question before attributing hesitation to the prominence of the seasonal photograph.
Pros
Category tiles give a practical continuation below the seasonal image.
Two visible actions clarify the campaign's shopping branches.
Cons & considerations
Campaign copy needs contrast checks against changing photographs.
Clothing suitability requires information not visible in the opening image.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Hotel Emma fills the opening view with a city-and-building photograph, a centered welcome and a compact crest above. The dark header provides a stable frame while the image supplies the sense of place. This makes the page a useful study in how an atmospheric introduction relates to a visitor's practical need for dates, room information and booking access.
What you can learn
Choose a concrete planning task before reviewing interaction evidence. A visitor enjoying the photograph and a visitor struggling to find availability may pause in the same place. A public tracking initializer cannot distinguish those intentions or establish how a separate booking system treats personal information. Confirm which practical information the participant needs first, since an attractive destination introduction and a useful booking route solve different problems.
Pros
The building photograph provides a specific sense of location.
A restrained header leaves the destination image uncluttered.
Cons & considerations
Large atmosphere-led content postpones detailed room comparisons.
Reservation handoffs need independent checks beyond the public homepage.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Verso's captured homepage pairs a left-hand promotion with several new-title cards across the remaining width. The small red wordmark and compact category navigation leave most of the space to books. This creates a more explicitly catalog-oriented opening than a full-screen campaign, with several concrete titles visible before a visitor starts scrolling.
What you can learn
Study whether a reader arriving for a known author can distinguish title, subject and promotional routes. Use that question to interpret the sequence rather than treating every extra click as friction. The script association does not provide private reading history, conversion evidence or proof that an optional tracking feature is enabled. Check whether readers understand which titles belong to the promotion before changing the balance between the campaign and new-book cards.
Pros
Several covers and titles are visible without leaving the first screen.
The campaign is one entry point rather than the only dominant object.
Cons & considerations
Compact card text needs review on narrow screens and zoomed layouts.
Many simultaneous titles can make the primary next step less obvious.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Noma opens with a large photograph of its building and garden, a small location-and-season line and a booking invitation at the lower left. Minimal navigation sits across the top of the image. The restrained composition makes the physical setting central, while practical information competes with the scale and detail of the photograph.
What you can learn
Set a bounded research question around finding the correct season or reservation information. Do not infer that pauses on imagery indicate intent to book. A Hotjar initializer reference says nothing about a visitor's preferences, actual recording, reservation availability or the privacy behavior of an external booking service. Ask what seasonal information a visitor expects after the booking link, then compare that expectation with the actual public destination.
Pros
The building and garden establish a distinctive physical setting.
The seasonal booking invitation is explicit rather than implied by imagery.
Cons & considerations
Small text over photography requires careful contrast and focus treatment.
A minimal opening can postpone important practical dining information.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Intelligentsia presents a brewing vessel and coffee package against a vivid orange background. A compact seasonal label and action sit to the side, while the permanent navigation remains on a pale header. A consent box covers part of the lower-left area, making consent state an important consideration when assessing what visitors actually see first.
What you can learn
Compare the product-story route with a direct coffee-selection task, and account for the consent interface in the test setup. The cached Hotjar reference does not prove that recording occurs before or after a choice. Do not use the visual warmth of the campaign as evidence of purchasing behavior. Keep consent state consistent within a comparison, or explicitly record it as a variable rather than silently mixing different first-screen experiences.
Pros
The strong palette makes the product arrangement easy to recognize.
Permanent shopping categories remain distinct from the campaign.
Cons & considerations
The consent box changes the visible balance of the opening view.
Seasonal copy may not answer a returning buyer's product-specific question.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
The Newt in Somerset leads with a winter-themed editorial photograph and expressive centered lettering. A light header lists several destination activities rather than reducing the property to a single booking action. The opening feels like a magazine feature, which makes it useful for considering how storytelling coexists with visitors seeking practical plans.
What you can learn
Separate accommodation, visiting and other destination tasks in the research plan. A broad editorial feature can serve different audiences differently, so avoid combining every route into one assumed funnel. The public Hotjar reference supports only an association with the sampled page, not evidence of visitors' movements or decisions. Use distinct scenarios for day visitors and overnight guests so a successful route for one audience is not misread as universal.
Pros
The seasonal image creates a distinct editorial identity.
Activity navigation acknowledges more than one reason to visit.
Cons & considerations
Decorative lettering needs readable alternatives and careful image contrast.
Multiple destination activities can make one universal success metric misleading.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Gerald Edelman places a concise business-leader statement over a mountain photograph, with a narrow navigation row above. Large red graphic curves give the image a recognizable brand frame. The opening emphasizes continuity and confidence rather than listing every service, leaving the menu to connect the broad proposition with a visitor's specific advisory need.
What you can learn
Use a realistic service-finding task rather than a vague instruction to explore. Observe whether the broad promise helps people choose a relevant route, without interpreting dwell time as trust. A Hotjar script reference is not evidence about inquiry quality, private financial information or the effectiveness of the firm's advice. Ask participants to explain the service they expect behind a navigation label before using their click as evidence of fit.
Pros
The main proposition is short enough to scan quickly.
The red graphic treatment gives the photograph a distinctive brand context.
Cons & considerations
A broad promise can delay evidence of specific service fit.
Professional inquiries may contain information unsuitable for behavioral capture.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Smith Teamaker gives a new tea release a split presentation: a large package image on one side and a dark text panel on the other. The top navigation includes shopping, gifts and repeat-order possibilities. The page therefore offers both a particular product story and practical routes for visitors who already know the brand.
What you can learn
Study a returning purchaser and a first-time gift shopper as different tasks. Evaluate whether the featured release assists either route rather than assuming it must be the desired destination. A sampled Hotjar initializer does not establish recorded customer behavior, subscription changes or the results of any checkout. Include a task involving a familiar tea, since a repeat buyer may reasonably avoid the newly featured release altogether.
Pros
Packaging and product name appear together within one clear feature.
The header offers routes that do not depend on the new release.
Cons & considerations
A dominant launch can overshadow familiar products for repeat buyers.
Subscription and order information need explicit capture exclusions.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Drost combines a garden and water-feature photograph with a pale text panel naming irrigation. The green header separates service categories, while the hero's large image supplies project context. The arrangement suggests a broader services portfolio without asking the photograph alone to explain what the business does or which route a visitor should take.
What you can learn
Choose a task such as finding irrigation information or locating a suitable contact route. Observe whether the service label aligns with the visitor's understanding before changing the design. The source association does not reveal real lead behavior, property addresses or whether Hotjar actually records the inquiry interface. Keep the scenario grounded in an actual service need, and avoid collecting a real property address merely to evaluate the interface.
Pros
A specific service label accompanies the project photography.
The green navigation establishes a consistent frame above the work.
Cons & considerations
A single featured service may underrepresent the wider portfolio.
Inquiry forms need suppression and consent planning before behavioral study.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Square Mile Coffee pairs a landscape photograph with large campaign lettering and a restrained white navigation. Immediately below, a bold whole-bean heading and compact category controls make the shopping context explicit. The contrast between the scenic opening and the practical next section is useful for studying where a visitor changes from exploration to selection.
What you can learn
Define a question around reaching an appropriate coffee category, then compare the hero and direct-navigation routes. Do not interpret a scenic image pause as buying intent. Public Hotjar references identify a sampled implementation detail, not recording settings, customer preferences or evidence that the campaign increases sales. Check whether participants recognize the category controls below the image before assuming that the scenic introduction is the source of hesitation.
Pros
The shopping section names the product type directly below the image.
Compact category controls offer alternatives to the featured release.
Cons & considerations
Campaign lettering over scenery needs crop-aware contrast checks.
A scenic feature does not communicate all product-selection criteria.
Platform source: Dated public source inspection. The dated sampled public page or its first-party script includes Hotjar initializer configuration or the static.hotjar.com/c/hotjar- loader construction. This is stronger than a preconnect or CSP allowlist alone, but does not prove execution, active recording, consent configuration or collected data. Platform evidence is separate from the direct website screenshot and is not a complete current infrastructure audit.
Kegan has 15+ years of experience working with small businesses, Fortune 500 companies, and everything in between. No development job is too big or too small: he brings the same hands-on attention to a focused improvement, a complete website, or a custom application.
For Hotjar projects, he can help with website integrations, form and campaign connections, analytics implementation, testing, and clear ownership after launch. He works directly with clients on scope, design, implementation, testing, and handover, with an emphasis on clear communication and a system that remains practical to maintain after launch.
Show 3 other Hotjar developersHide other Hotjar developers
Give a participant a concrete question and examine whether the interface leads to an appropriate answer. Distinguish category comprehension, query formulation and result usefulness. Avoid collecting pasted secrets, private configuration or unnecessary search content.
Shopping and product discovery
Separate a known-item task from open-ended gift or category exploration. A campaign may help one and distract from another. Keep interpretations tied to the task rather than treating a visually prominent image or long pause as evidence of purchase intent.
Services and practical planning
Study the route to a relevant location, service explanation or public booking handoff. Use controlled scenarios and nonpersonal test information. Do not submit real inquiries, bookings or account changes merely to evaluate a page layout.
From references to requirements
Turn observations into a defensible design decision
Write down the hypothesis
Identify the label, component or route you think creates a problem. Explain what competing interpretation could also fit the observed behavior. A person may bypass a feature because they understand the site well, not because the feature is broken.
Keep the test context consistent
Record the task, device class and consent state. A banner can materially change the first screen, so do not silently compare a clean view with an obstructed one. Use representative content and identify which states were not evaluated.
Make a small change and check again
Translate findings into a bounded change with a clear expected effect. Verify that it preserves neighboring tasks and accessibility. Keep a record of evidence and limitations instead of turning a small observation into a claim about all visitors.
A useful handover demonstration
Ask the actual team to carry out its routine job: publish a realistic update, correct a mistake, preview a narrow screen, and identify who owns an integration failure. For a library or frontend framework, also ask who maintains the content source and deployment. A polished screenshot does not answer those operational questions.
Beyond the screenshot
Behavioral-research planning checklist
Define a task and an audience before collecting observations.
Write the design question and competing explanations.
Verify your own tracking setup through authorized access.
Review consent, sensitive routes and suppression needs.
Keep personal details and proprietary search inputs out of the study.
Record viewport and consent state when comparing behavior.
Corroborate ambiguous pauses or repeated clicks with direct questions.
Recheck the chosen change against adjacent visitor tasks.
Test with real content, a keyboard, a small screen, slow or failed requests, and the people who will maintain the system. These are planning checks, not an accessibility, security, performance, or search-ranking certification.
Sources & editorial method
How this Hotjar collection was reviewed
Twenty distinct public properties were selected from previously documented source pages and dated public technology observations. The direct browser captures retain their original source URLs, capture dates, dimensions and attribution. The new collection-specific reviews describe visible composition and planning implications separately from technical evidence. Previously recorded source observations were rechecked without being relabeled as fresh observations. The retained screenshots were visually re-reviewed; no real form, account, purchase or booking was submitted. Inclusion requires a Hotjar initializer or loader construction in a sampled public page or first-party script. CSP entries, preconnects and unspecific proxy settings alone were rejected. Configuration can be conditional or serialized, so the evidence does not prove execution, recording, consent choices or actual visitor behavior.
Every image is an unmodified capture from the actual website, with its source and capture date. Some captures are reused from our shared catalog; their dates remain the original capture dates. None comes from a vendor gallery or a generated reconstruction. Moving imagery and live content can change.
Technology attribution uses public page assets or metadata, official platform documentation, or a cited first-party project case study. Documentary and framework-relationship evidence is identified where used; it is not a complete current backend inventory. A CMS image CDN alone does not establish a full CMS deployment. A library’s presence does not prove which individual controls use it, and a platform label does not establish AI authorship.
The composition notes, lessons, pros and tradeoffs are original editorial observations. We have not measured conversion, traffic, security, performance or accessibility conformance. Website owners retain their brands and imagery; these examples are not our client portfolio. Written, Edited and Curated are independent records, not dates advanced by a build. See our editorial standards or suggest a correction.
Questions worth asking
Hotjar website development FAQs
Does this guide show Hotjar recordings?
No. It reviews public screenshots and dated source references. No private recordings, heatmaps, account data or participant information were accessed.
Does a source reference prove the tool is active?
No. An initializer or loader reference is stronger evidence than a DNS hint, but may still be conditional or unused. Actual collection requires separate authorized verification.
Can a pause tell me that a visitor is confused?
Not by itself. A pause may mean reading, distraction, deliberation or difficulty. Interpret it alongside the task and other evidence instead of assigning a motive automatically.
Why keep the old screenshot and observation dates?
The capture and technical observation describe specific moments. This guide adds new analysis without presenting reused evidence as a newly observed live state.
