1,744
Raw sessions
▲ 13.4%
July recorded 1,744 raw sessions, up 13.4% from June, while button, email, and phone actions fell from 48 to 34. Organic search stayed small but action-oriented: 193 sessions produced 15 of 28 filtered action sessions, a 7.8% rate against direct traffic's 1.0%. Technical reliability needs immediate work — PostHog recorded 1,159 exception events across 206 sessions, and Largest Contentful Paint (LCP) reached 7,134 ms at the 75th percentile (p75). Eleven taskboard items were marked complete. August should validate attribution, fix production reliability, and improve the main commercial pages before adding more pages.
1,744
Raw sessions
▲ 13.4%
193
Organic search
▲ 1.0%
34
Raw actions
▼ 29.2%
1,159
Exceptions
206 sessions
Changes are measured against June: 1,538 sessions, 191 organic-search sessions, and 48 tracked actions. Filtered July actions total 32. Source: PostHog, July 1–31, 2026. Raw totals include non-production sessions and PostHog-detected bots; filtered totals exclude both. Previous-period comparisons use June only where a verified June figure exists.
Raw sessions increased from 1,538 in June to 1,744 in July, while raw tracked actions fell from 48 to 34. After removing non-production sessions and PostHog-detected bots, the reporting view contains 1,490 sessions, 1,322 visitors, 2,710 pageviews, and 32 tracked actions. The website attracted more visits without a corresponding increase in recorded intent. Next action: reconcile button, email, and phone events with successful form submissions and customer relationship management records, and report confirmed inquiries separately from interactions.
Filtered Sessions
1,490
Production, not detected as bot
Visitors
1,322
Filtered production
Pageviews
2,710
Filtered production
Tracked Actions
32
Filtered · 34 raw
July Sessions by Reporting Status
1490
214
40
Session-based. Reported = 1,490 production sessions not detected as bots. Bot = 214 production sessions detected as bots. Non-prod = 40 non-production sessions. Only reported sessions enter the reporting view.
Production Sessions by Channel
Direct
1,244 · 83.5%
Organic search
193 · 13.0%
Referral
40 · 2.7%
Organic social
10 · 0.7%
1 · 0.1%
Organic video
1 · 0.1%
Unmatched
1 · 0.1%
Direct traffic dominates volume but produces the lowest action-session rate. See section 05.
| Channel | Sessions | Share |
|---|---|---|
| Direct | 1,244 | 83.5% |
| Organic search | 193 | 13.0% |
| Referral | 40 | 2.7% |
| Organic social | 10 | 0.7% |
| 1 | 0.1% | |
| Organic video | 1 | 0.1% |
| Unmatched | 1 | 0.1% |
The homepage recorded 1,072 pageviews from 899 sessions and 778 visitors. It was the entry page for 886 sessions and had a 23.3% bounce rate. No other page approached its reach, so most prospective customers encounter the broad company message before they see service-specific proof. Next action: clarify the Tampa Bay construction offer, place the strongest project evidence earlier, and route visitors to priority services and contact options. Strengthen the highest-value service pages next.
Homepage Pageviews
1,072
From 899 sessions · 778 visitors
Homepage Entries
886
Entry page for 886 sessions
Homepage Bounce Rate
23.3%
June: 23.5% measured
| # | Page | Pageviews | Sessions | Visitors |
|---|---|---|---|---|
| 1 | Homepage | 1,072 | 899 | 778 |
| 2 | Team | 241 | 171 | 127 |
| 3 | Projects | 214 | 178 | 158 |
| 4 | About | 106 | 76 | 62 |
| 5 | Contact | 90 | 73 | 64 |
| 6 | Greater Tampa Realtors project | 66 | 66 | 66 |
| 7 | Services | 66 | 49 | 41 |
| 8 | Motor Enclave HQ project | 54 | 48 | 45 |
| 9 | Trade Partners | 44 | 33 | 24 |
| 10 | TIA roof project | 30 | 28 | 28 |
Core Web Vitals track loading speed, visual stability, and responsiveness. First Contentful Paint (FCP) averaged 1,390 ms, and Interaction to Next Paint (INP) recorded a 64 ms p75 — about 65 ms on average after excluding two severe daily anomalies. Largest Contentful Paint (LCP) exceeded 4,000 ms on five days and reached 9,471 ms on July 10. Cumulative Layout Shift (CLS) reached 0.571, 0.407, and 0.278 on July 23–25, and INP reached 4,057 ms on July 27 and 42,749 ms on July 28. Next action: compare those dates with deployment history, script changes, image behavior, and third-party activity. The timing indicates isolated events, but the available data does not identify the cause.
Average LCP
2,297
ms · p75 7,134 ms across 927 samples
Average FCP
1,390
ms · good threshold under 1,800 ms
p75 INP
64
ms · outside the July 27–28 anomalies
Severe Days to Investigate
July 10 — LCP
9,471 ms
July 10 — FCP
5,325 ms
July 23 — CLS
0.571
July 24 — CLS
0.407
July 25 — CLS
0.278
July 27 — INP
4,057 ms
July 28 — INP
42,749 ms
Daily peaks, not monthly averages. Each date needs a deployment and third-party script comparison.
Reading the Two Numbers
01
FCP averaged 1,390 ms against an 1,800 ms good threshold, and INP p75 was 64 ms against a 200 ms threshold. The everyday experience is not the problem.
02
LCP averaged 2,297 ms but reached 7,134 ms at p75 across 927 samples. CLS averaged 0.125 against a 0.10 threshold and reached 0.186 at p75.
03
The gap between the monthly average and p75 indicates volatility, not a calculation error. Fix the volatility before treating the averages as a baseline.
| # | Metric | Monthly average | p75 | p75 samples | Good threshold | Assessment | Observed issue |
|---|---|---|---|---|---|---|---|
| 1 | LCP | 2,297 ms | 7,134 ms | 927 | <2,500 ms | Borderline average; poor p75 | Five days exceeded 4,000 ms; July 10 reached 9,471 ms |
| 2 | FCP | 1,390 ms | Not available | n/a | <1,800 ms | Good | July 10 reached 5,325 ms; otherwise stable |
| 3 | CLS | 0.125 | 0.186 | 771 | <0.10 | Needs improvement | July 23–25 reached 0.571, 0.407, and 0.278 |
| 4 | INP | 65 ms (excludes anomalies) | 64 ms | 202 | <200 ms | Good outside anomalies | July 27 reached 4,057 ms; July 28 reached 42,749 ms |
PostHog recorded 1,159 exception events across 206 sessions and 202 visitors. The largest unhandled homepage group produced 631 events across 74 sessions; the next two produced 165 and 138. Exception events are not unique defects, but the frequency and session reach of the largest group make it the first technical priority. Next action: group the events by error signature, reproduce the three largest issues, and compare their timing with the Web Vitals anomalies. Fix the issue affecting the most sessions, then add a production regression check.
Exception Events
1,159
July, connected PostHog project
Affected Sessions
206
13.8% of filtered production sessions
Affected Visitors
202
Distinct
| Issue group | Events | Sessions | Handled |
|---|---|---|---|
| Unhandled homepage issue 1 | 631 | 74 | No |
| Unhandled homepage issue 2 | 165 | 19 | No |
| Unhandled homepage issue 3 | 138 | 41 | No |
Organic search produced 15 action sessions from 193 sessions, a 7.8% rate. Direct traffic produced 13 from 1,244, a 1.0% rate. Organic search represented 13.0% of filtered sessions but 53.6% of filtered action sessions. The total is still small, and the actions are not confirmed leads. Next action: identify the organic landing pages and queries that contributed to these actions, add a confirmed form-success event, and reconcile the results with customer relationship management records.
Organic search action sessions
15
Direct action sessions
13
All filtered action sessions
28
Filtered tracked actions
32
Tracked actions include button, email, and phone interactions. They are not confirmed submissions, qualified leads, opportunities, or revenue.
Action-Session Rate by Channel
7.8%
Organic search · 15 of 193 sessions
1.9%
All filtered production · 28 of 1,490
1.0%
Direct · 13 of 1,244 sessions
Action sessions divided by all sessions in the same channel. Organic search is 13.0% of filtered sessions but 53.6% of filtered action sessions.
| Channel | Action sessions | All sessions | Action-session rate |
|---|---|---|---|
| Organic search | 15 | 193 | 7.8% |
| All filtered production | 28 | 1,490 | 1.9% |
| Direct | 13 | 1,244 | 1.0% |
The July taskboard marks 11 items complete. They cover Search Console, Google Analytics, event tracking, funnel events, the Trade Partners form, image optimization, spam mitigation, and the /store page. The team can now observe more of the path from a website visit to a high-intent action. A completed task does not prove business impact: the public taskboard does not show owners, completion dates, acceptance criteria, or validation results. Next action: add an owner, completion date, validation evidence, and outcome measure to every completed task.
| # | Completed task | Outcome area | Status |
|---|---|---|---|
| 1 | Established Search Console baseline | SEO measurement | Complete |
| 2 | Updated Google DNS to address spam | Traffic quality | Complete |
| 3 | Added event tracking | Measurement | Complete |
| 4 | Embedded the form on the Trade Partners page | Conversion | Complete |
| 5 | Added bottom-funnel events | Measurement | Complete |
| 6 | Added the /store page | Content | Complete |
| 7 | Added top-funnel events | Measurement | Complete |
| 8 | Added Trade Partner funnel events | Measurement | Complete |
| 9 | Completed additional image optimization | Performance | Complete |
| 10 | Added middle-funnel events | Measurement | Complete |
| 11 | Added Google Analytics | Measurement | Complete |
Four evidence-based positives from July: measurement coverage, organic-search intent, baseline speed, and project-page interest. Each is measured from the filtered production view unless stated otherwise.
01
The taskboard marks Search Console, Google Analytics, and top-, middle-, bottom-, and Trade Partner funnel events as complete.
02
Organic search accounted for 13.0% of filtered sessions and 53.6% of filtered action sessions, a 7.8% action-session rate.
03
FCP averaged 1,390 ms, and INP p75 was 64 ms outside the July 27–28 anomaly.
04
The Greater Tampa Realtors and Motor Enclave HQ pages ranked among July's ten most-viewed pages.
Complete measurement and stability work before expansion. Finish attribution and production crawlability before adding pages, then improve the commercial pages that already attract visits and connect project content to services, sectors, and contact paths. The local landing-page plan and keyword glossary remain useful, but page production should wait until service-area demand, page ownership, and measurement are reliable. Keep documentation and ownership current throughout the work.
| # | Priority | Current status | Next action | Win condition |
|---|---|---|---|---|
| 1 | Trust lead and attribution measurement | Data Dictionary in progress | Confirm production events, form success, channel rules, human-traffic filters, and customer relationship management reconciliation. | Each qualified inquiry has one source and no duplicate count. |
| 2 | Enforce production crawlability | Technical SEO baseline in progress | Add route smoke tests and release gates. Resolve sitemap ownership, redirects, project rendering, the tenant-improvements mismatch, and the legacy /store/ plan. | Canonical routes return stable server-rendered 200 responses. Redirects take one hop, and the sitemap lists only canonical 200 URLs. |
| 3 | Upgrade core acquisition pages | Local landing-page plan not started | Improve the homepage and priority service pages with buyer problems, proof, service-area context, and clear contact actions. Publish location pages only after validating demand and page ownership. | Organic entry sessions produce more qualified actions. |
| 4 | Build a structured proof network | Next | Standardize project facts, label joint-venture work, and connect each project to services, sectors, locations, constraints, outcomes, and contact paths. | Project and sector pages gain non-branded visibility and contribute to qualified inquiries. |
| 5 | Consolidate governance | Data Dictionary in progress | Maintain one project brief, architecture, measurement specification, and decision log with owners and dates. Close the remaining Vercel comments. | Each important fact and decision has an owner, source, verification state, and review date. |
Three Questions to Answer Before the August Report
01
Attribution cannot be trusted until one event marks a successful website form submission and is reconciled with customer relationship management records.
02
The 32 filtered tracked actions need to be traced to inquiries or opportunities before they are reported as commercial outcomes.
03
July 10, July 23–25, and July 27–28 need a comparison against deployment history and third-party script changes.
What This Report Does Not Prove
Tracked actions are button, email, and phone interactions
Not confirmed leads
Monthly averages and p75 measure different parts of the experience
Volatility, not error
The cause of the performance spikes is unconfirmed
Session recording disabled
The taskboard confirms status only
No owners or acceptance criteria
July comparisons use June only where a verified June figure exists. No unverified metrics were added.