Competitor intelligence dossier
benluong.com
Ben Luong is a Technical Google Analytics 4 (GA4) and Google Ads Consultant based in Ireland. He combines Computer Science with marketing to fix tracking, ensure compliance, and provide clean data for AI-driven campaign optimization.
60-second brief
What the site appears to sell, how it converts visitors, what is measurable and where the evidence is incomplete.
No matching public ad was verified in the sampled libraries. This does not prove that no campaigns are running.
5 public measurement or advertising signals were observed, including 1 legacy signal. Presence does not prove configuration quality or report receipt.
Cloudflare was observed at the public edge and WordPress was fingerprinted as the site platform. The origin host may remain hidden.
Ahrefs Domain Rating is a logarithmic backlink-strength metric. It is not a traffic estimate or a search-position score.
Mobile lab scored 98 out of 100. Response-time samples conflict: the bounded page fetch took 6.6 s, while the Lighthouse server-response audit reported 243 ms. Verify region and cache state before treating latency as a fault. No eligible public CrUX field sample was available; that is not a failed Core Web Vitals result.
Commercial read
A cautious interpretation of the public positioning, offers, proof, conversion routes, acquisition signals and content footprint.
AI Powered Google Analytics & Ads Consultant – Ben Luong. Ben Luong is a Technical Google Analytics 4 (GA4) and Google Ads Consultant based in Ireland. He combines Computer Science with marketing to fix tracking, ensure compliance, and provide clean data for AI-driven campaign optimization.
The sampled site promotes “🍓 Free Setups” and “1 Hour Booking”.
“Google Analytics Consultant Testimonials: What My Clients Are Saying” and supporting case-study, review or results routes provide public trust signals.
Website form was observed, alongside a booking or contact route. Submission handling and conversion firing were not tested.
Meta, Microsoft Advertising, Google and Google Analytics measurement or advertising technology is present. This suggests channel instrumentation, but does not prove that campaigns are active.
2,247 words were found on the sampled homepage, with case-studies and blog content routes. 5 exact-domain pages appeared in the bounded index-presence check.
Prioritised
Up to five practical actions, deduplicated and ordered by likely impact. Open each one for the evidence and verification path.
Confirm whether the legacy bootstrap is still needed and remove it if not.
Why it matters: Retired measurement code can add requests and create misleading expectations without a supported destination.
How to verify: Rescan the published page and container after removal.
Submit an authorised test lead, confirm the fields are stored on the receiving record, and verify any eligible outcome upload.
Why it matters: Retaining attribution through to qualified outcomes can improve campaign optimisation and reporting.
How to verify: Trace one authorised test click and lead from landing page to the receiving system.
Write a concise description for search and social previews.
Why it matters: Meta description helps people and search systems understand the page before visiting.
How to verify: Inspect the rendered head and a search preview.
Test and add Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, frame-embedding protection, Permissions-Policy and Referrer-Policy as appropriate. Roll out CSP in report-only mode first if the site has many third-party integrations.
Why it matters: CSP can limit the impact of injected content.
How to verify: Inspect the final response headers after deployment.
Repeat first-byte measurements from multiple regions with warm and cold caches before prioritising server work.
Why it matters: A single slow remote fetch may reflect route, cache or temporary origin conditions rather than a consistent visitor experience.
How to verify: Compare repeated TTFB measurements with real-user monitoring and edge-cache status.
Demand signals
Only strong ad matches are counted. The search sample checks exact-domain index presence; it is not a rankings report.
No matching public ad was verified in the sampled libraries. This does not prove that no campaigns are running.
5 exact-domain pages appeared in a bounded index-presence check. This is not a measure of wider query performance.
Ben Luong is a Technical Google Analytics 4 (GA4) and Google Ads Consultant based in Ireland. He combines Computer Science with marketing to fix tracking, ensure compliance, and provide clean data for AI-driven campaign optimization.
benluong.comWhy You Need a GA4 Expert 🍓 Google Analytics 4 isn't plug & play. If your GA4 isn't configured properly, you're losing valuable data - and money. 🍓 AI-powered insights mean nothing without clean data. Bad tracking = bad decisions. I ensure your GA4 setup provides accurate, actionable insights following all best practices for Ga4. 🍓 Consent banners are breaking your analytics ...
benluong.com › welcomeAbout anonymity: Client data is confidential. These case studies are anonymised and shown as ranges to respect NDAs and competitive sensitivity. About credibility: Many published case studies overstate impact. To avoid that, I only publish outcomes I can verify from source systems (GA4, Ads, CRM) and I label the source under each result. Detailed evidence is available under NDA. Complex ...
benluong.com › case-studiesI'm Ben, an online marketer who has been in the industry for over 20 years. I have a BEng in Computer Science from the University of York in the UK. After graduation, I found a job in email marketing for a company that was eventually bought by the DMGT.
benluong.com › aboutAug 27, 2025I've been conversing a lot with Grok recently to try and get my theories into the training sets, and here's what it says about machine ingestion. How the X Algorithm Works X's recommendation algorithm (primarily for the "For You" timeline) is a machine learning system that personalises content based on...
benluong.com › blogSpeed and experience
Lighthouse is a one-off lab test. CrUX is 28-day real-user data and may be unavailable on lower-traffic sites.
Mobile lab scored 98 out of 100. Response-time samples conflict: the bounded page fetch took 6.6 s, while the Lighthouse server-response audit reported 243 ms. Verify region and cache state before treating latency as a fault. No eligible public CrUX field sample was available; that is not a failed Core Web Vitals result.
Controlled Lighthouse lab result.
PageSpeed Insights could not complete this Lighthouse test.
No eligible public 28-day CrUX sample was returned for phone or desktop.
Needs verificationCore Web Vitals are LCP, INP and CLS measured from real users at the 75th percentile. Lighthouse is a synthetic test: it can diagnose LCP and CLS, while TBT is only a laboratory proxy for responsiveness and is not INP.
No public real-user verdict is available. The mobile Lighthouse lab test scored 98/100, which is useful for diagnosis but cannot prove how real visitors experience the site.
A one-off Lighthouse diagnostic. A score of 90 or higher is considered good, but it is not a real-user Core Web Vitals verdict.
Remove unused styles, split page-specific CSS and load non-critical styles after the first render. Estimated lab saving: up to 560 ms · 90.9 KB.
Source: Google PageSpeed Insights / Lighthouse · Profile: mobile · Tested: 4 September 2026 at 16:14 UTC · Lighthouse 13.4.1 · tested page
PageSpeed Insights could not complete this Lighthouse test.
PageSpeed Insights could not complete this Lighthouse test.
Source: Google PageSpeed Insights / Lighthouse · Profile: desktop
CrUX found no eligible mobile record for either the exact URL or the whole origin. This usually means there is not enough eligible public Chrome traffic for publication; it is not a failed performance score.
Use the Lighthouse lab result for today’s diagnosis. For a site you own, Search Console may show grouped CrUX data for the verified property. First-party real-user monitoring is the independent fallback when public data is absent.
Source: Chrome UX Report API · Exact URL and origin fallback checked · CrUX eligibility methodology
CrUX found no eligible desktop record for either the exact URL or the whole origin. This usually means there is not enough eligible public Chrome traffic for publication; it is not a failed performance score.
Use the Lighthouse lab result for today’s diagnosis. For a site you own, Search Console may show grouped CrUX data for the verified property. First-party real-user monitoring is the independent fallback when public data is absent.
Source: Chrome UX Report API · Exact URL and origin fallback checked · CrUX eligibility methodology
Remove unused styles, split page-specific CSS and load non-critical styles after the first render. Estimated lab saving: up to 560 ms · 90.9 KB.
PageSpeed Insights could not complete this Lighthouse test. This is not a poor score.
Search Console may show grouped CrUX data for a verified property. If it does not, install privacy-conscious first-party real-user monitoring; INP cannot be judged from Lighthouse alone.
Receipts
The supporting stack, measurement, infrastructure, reputation and raw collection modules. Kept compact until you need it.
Meta Pixel · Universal Event Tracking · Google tag, GA4, Ads or Floodlight · Cloudflare · WordPress
Meta Pixel · Microsoft UET · Google tag / GA4 · Universal Analytics (legacy) · Google Tag Manager
Cloudflare was observed at the edge. The origin hosting provider may be hidden behind it.
published Google Tag Manager container · 1 signal · view sampled page
published Google Tag Manager container · 1 signal · view sampled page
published Google Tag Manager container · 1 signal · view sampled page
published Google Tag Manager container · 1 signal · view sampled page
published Google Tag Manager container · 1 signal · view sampled page
published Google Tag Manager container · 1 signal · view sampled page
browser network request · 1 signal · view sampled page
published Google Tag Manager container · 1 signal · view sampled page
published Google Tag Manager container · 1 signal · view sampled page
browser network request · 1 signal · view sampled page
browser network request · 1 signal · view sampled page
No match is not a safety guarantee. Investigate any warning independently.
Open any card to inspect the public evidence, source and collection details.
373.6 KB of public HTML inspected
HTTP 200 · 221.9 KB · 6.6 s · view sampled page
HTTP 200 · 151.7 KB · 10 ms · view sampled page
354 browser requests observed before interaction
HTTP 200 · 137 requests · 16 third-party hosts · view sampled page
HTTP 200 · 217 requests · 13 third-party hosts · view sampled page
Fresh browser context; no forms or logins submitted
Meta Pixel · Universal Event Tracking · Google tag, GA4, Ads or Floodlight
Meta Pixel · Advertising · 100% confidence
Universal Event Tracking · Advertising · 100% confidence
Google tag, GA4, Ads or Floodlight · Analytics and data · 100% confidence
Cloudflare · CDN and edge · 100% confidence
WordPress · CMS · 95% confidence
jQuery · JavaScript library · 95% confidence
Universal Analytics code · Legacy technology · 100% confidence
Container bootstrap · Tag management · 100% confidence
1 address · 2 nameservers · 1 mail routes
Domain: benluong.com
A: 1 record
NS: 2 records
MX: 1 record
TXT: 3 records
SOA: 1 record
Email policy: SPF present · DMARC not observed
Registration currently expires 8 Mar 2029
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com (303)
Registered: 8 Mar 2012
Expires: 8 Mar 2029
Nameservers: jon.quicns.net, kevin.quicns.cloud
Registry RDAP via the IANA bootstrap · https://rdap.verisign.com/com/v1/domain/benluong.com
135.125.104.145 · FR
Network allocation: SD-GRA2-G265-FAT-MAGGIE-SDAGG63-1
Address: 135.125.104.145
Registry country: FR
Edge detection confidence: high
Cloudflare was observed at the edge. The origin hosting provider may be hidden behind it.
Mobile Lighthouse performance
FCP: 1.8 s
LCP: 1.9 s
CLS: 0
TBT: 10 ms
Mobile real-user Core Web Vitals: no public CrUX sample; this is not a failed score
Desktop real-user Core Web Vitals: no public CrUX sample; this is not a failed score
Top lab opportunity: Reduce unused CSS · up to 560 ms · 90.9 KB
No current Google Web Risk match
Google Web Risk: no current match
Reputation data is a provider snapshot, not a warranty that a site is safe. Timestamps and coverage matter.
Backlink profile strength on a logarithmic 0-100 scale. It is not a Google ranking or traffic metric.
robots.txt found · 3 sitemap declarations
robots.txt · 2.8 KB · view sampled page
User-agent directives: present
Declared sitemap · view sampled page
Declared sitemap · view sampled page
Declared sitemap · view sampled page
XML index · 661 B
No file returned from the standard public location
Checked /.well-known/security.txt · view sampled page
Absence is informational and is not a vulnerability by itself
11 priority findings · 85% scored evidence coverage
Deterministic ruleset 0.1.0
Report generated: 4 September 2026 at 16:14 UTC
Rules produced 11 prioritised findings
One bounded scanner fetch took 6.6 s, while the Lighthouse server-response audit reported 243 ms. These samples conflict.
Suggested fix: Repeat first-byte measurements from multiple regions with warm and cold caches before prioritising server work.
Why it matters: A single slow remote fetch may reflect route, cache or temporary origin conditions rather than a consistent visitor experience.
How to verify: Compare repeated TTFB measurements with real-user monitoring and edge-cache status.
Universal Analytics code
Suggested fix: Confirm whether the legacy bootstrap is still needed and remove it if not.
Why it matters: Retired measurement code can add requests and create misleading expectations without a supported destination.
How to verify: Rescan the published page and container after removal.
The header was absent from the sampled final HTML response.
Suggested fix: Add a tested Content-Security-Policy. Start in report-only mode if necessary.
Why it matters: CSP can limit the impact of injected content.
How to verify: Inspect the final response headers after deployment.
Public form markup includes cf7atr_click_id and cf7atr_click_id_type and 10 UTM or referrer fields. The public scan cannot confirm that submitted values reach the CRM or advertising platforms.
Suggested fix: Submit an authorised test lead, confirm the fields are stored on the receiving record, and verify any eligible outcome upload.
Why it matters: Retaining attribution through to qualified outcomes can improve campaign optimisation and reporting.
How to verify: Trace one authorised test click and lead from landing page to the receiving system.
The header was absent from the sampled final HTML response.
Suggested fix: Add a suitable Strict-Transport-Security policy after confirming every subdomain is HTTPS-ready.
Why it matters: HSTS tells supporting browsers to keep using HTTPS.
How to verify: Inspect the final response headers after deployment.
Ben Luong is a Technical Google Analytics 4 (GA4) and Google Ads Consultant based in Ireland. He combines Computer Science with marketing to fix tracking, ensure compliance, and provide clean data for AI-driven campaign optimization.
Suggested fix: Write a concise description for search and social previews.
Why it matters: Meta description helps people and search systems understand the page before visiting.
How to verify: Inspect the rendered head and a search preview.
The header was absent from the sampled final HTML response.
Suggested fix: Set X-Content-Type-Options: nosniff.
Why it matters: X-Content-Type-Options reduces MIME confusion.
How to verify: Inspect the final response headers after deployment.
No frame-embedding restriction was observed
Suggested fix: Set CSP frame-ancestors or X-Frame-Options where legacy support is needed.
Why it matters: Clickjacking protection reduces unwanted framing.
How to verify: Repeat the same public check after the change.
The header was absent from the sampled final HTML response.
Suggested fix: Set a restrictive Permissions-Policy for unused browser capabilities.
Why it matters: Permissions-Policy limits access to powerful browser features.
How to verify: Inspect the final response headers after deployment.
The header was absent from the sampled final HTML response.
Suggested fix: Set an explicit Referrer-Policy appropriate to the site.
Why it matters: A referrer policy limits URL information sent to other origins.
How to verify: Inspect the final response headers after deployment.
No DS record was returned. This does not test every resolver or validate the complete chain.
Suggested fix: Consider enabling DNSSEC with coordinated registrar and DNS-provider configuration.
Why it matters: DNSSEC can provide origin authentication for DNS answers when the validation chain is correct.
How to verify: Validate the complete chain with an independent DNSSEC tool.
Bounded analysis of publicly accessible pages, DNS, registries and configured providers. No login, form submission, port scan or exploit testing.