Competitor intelligence dossier
lockdoctor.ie
A bounded public-evidence dossier for lockdoctor.ie.
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.
1 public measurement or advertising signal was observed. Presence does not prove configuration quality or report receipt.
Cloudflare was observed at the public edge. 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.
Desktop lab scored 65 out of 100. Lighthouse reported a 7 ms server response in that run. 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.
The sampled homepage did not expose a clear public positioning statement.
No distinct offer was confirmed from the sampled headings and routes.
No case-study, testimonial or review proof was confirmed in the bounded sample.
Click-to-call link was observed. Submission handling and conversion firing were not tested.
Google measurement or advertising technology is present. This suggests channel instrumentation, but does not prove that campaigns are active.
0 words were found on the sampled homepage. 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.
Implement and test a consent platform appropriate to the site's regions and data uses.
Why it matters: Consent state can determine which storage and requests are permitted. Automated detection is not a legal conclusion.
How to verify: Trace baseline, reject and accept sessions in fresh browser contexts.
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.
Write a unique, descriptive title that matches the page purpose.
Why it matters: Page title helps people and search systems understand the page before visiting.
How to verify: Inspect the rendered head and a search preview.
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.
Ireland's nationwide locksmiths. Fifteen owned bases · 26 counties · car keys, lock changes, emergency lockouts. Trading since 2007. PSA 04216.
lockdoctor.ie › wpLock Doctor is Ireland's premier Locksmith & Security Solutions supplier. We provide a 24 hour locksmith service nationwide across Ireland. As a result of a combined experience of over 20 years, Lock Doctor has earned a reputation for being a rapid response emergency locksmiths service.
wp.lockdoctor.ieResidential locksmith Ireland — house lockouts, lock changes, lost keys, security upgrades. Nationwide. Lock Doctor since 2007. Call 061 305 664.
lockdoctor.ie › wp › domestic-securityGet in touch with your local Lock Doctor. 15 locations across Ireland. Call, email, or send an enquiry. Find your nearest team.
lockdoctor.ie › wp › contact-usFind your nearest locksmith in Ireland. 15 Lock Doctor locations covering every county. Replacement car keys, lock changes, lost keys, lockouts.
lockdoctor.ie › wp › locksmith-near-meSpeed and experience
Lighthouse is a one-off lab test. CrUX is 28-day real-user data and may be unavailable on lower-traffic sites.
Desktop lab scored 65 out of 100. Lighthouse reported a 7 ms server response in that run. No eligible public CrUX field sample was available; that is not a failed Core Web Vitals result.
Configure PAGESPEED_API_KEY to run Lighthouse through PageSpeed Insights.
Controlled Lighthouse lab result.
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 desktop Lighthouse lab test scored 65/100, which is useful for diagnosis but cannot prove how real visitors experience the site.
Configure PAGESPEED_API_KEY to run Lighthouse through PageSpeed Insights.
Configure PAGESPEED_API_KEY to run Lighthouse through PageSpeed Insights.
Source: Google PageSpeed Insights / Lighthouse · Profile: mobile
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.
Open the Lighthouse diagnostic, address the largest estimated saving first, then rerun the same page and device profile. Estimated lab saving: up to 242 ms.
Remove dead JavaScript, split large bundles and defer code that is not needed for the first view. Estimated lab saving: up to 40 ms · 199.2 KB.
Open the Lighthouse diagnostic, address the largest estimated saving first, then rerun the same page and device profile. Estimated lab saving: 2.9 KB.
Source: Google PageSpeed Insights / Lighthouse · Profile: desktop · Tested: 4 September 2026 at 10:07 UTC · Lighthouse 13.4.1 · tested page
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
Open the Lighthouse diagnostic, address the largest estimated saving first, then rerun the same page and device profile. Estimated lab saving: up to 242 ms.
Remove dead JavaScript, split large bundles and defer code that is not needed for the first view. Estimated lab saving: up to 40 ms · 199.2 KB.
Open the Lighthouse diagnostic, address the largest estimated saving first, then rerun the same page and device profile. Estimated lab saving: 2.9 KB.
Improve LCP by prioritising the main image or content block, reducing render-blocking resources and shortening server delay. Lighthouse rates this poor in the current lab run.
Improve CLS by reserving dimensions for images, adverts and embeds, and avoiding late content insertion above existing content. Lighthouse rates this needs improvement in the current lab run.
Configure PAGESPEED_API_KEY to run Lighthouse through PageSpeed Insights. 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.
Google tag, GA4, Ads or Floodlight · Cloudflare
Google tag / GA4
Cloudflare was observed at the edge. The origin hosting provider may be hidden behind it.
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.
174 B of public HTML inspected
HTTP 202 · 174 B · 88 ms · view sampled page
22 browser requests observed before interaction
HTTP 200 · 22 requests · 8 third-party hosts · view sampled page
Fresh browser context; no forms or logins submitted
Google tag, GA4, Ads or Floodlight · Cloudflare
Google tag, GA4, Ads or Floodlight · Analytics and data · 100% confidence
Cloudflare · CDN and edge · 100% confidence
1 address · 2 nameservers · 1 mail routes
Domain: lockdoctor.ie
A: 1 record
NS: 2 records
MX: 1 record
TXT: 6 records
SOA: 1 record
Email policy: SPF present · DMARC present
Public registry record inspected
No additional public evidence was returned.
35.214.35.224
Network allocation: GOOGLE-CLOUD
Address: 35.214.35.224
Edge detection confidence: high
Cloudflare was observed at the edge. The origin hosting provider may be hidden behind it.
Desktop Lighthouse performance
FCP: 0.8 s
LCP: 3.6 s
CLS: 0.21
TBT: 170 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: Avoid multiple page redirects · up to 242 ms
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 · 0 sitemap declarations
robots.txt · 184 B · view sampled page
User-agent directives: not observed
XML unknown · 185 B
200 B public disclosure file
Checked /.well-known/security.txt · view sampled page
17 priority findings · 68% scored evidence coverage
Deterministic ruleset 0.1.0
Report generated: 4 September 2026 at 10:07 UTC
Rules produced 17 prioritised findings
No supported consent interface was identified in the fresh pre-consent browser state. This is not proof that the site has no banner: region, timing, prior-state logic and unsupported CMPs can change the result.
Suggested fix: Implement and test a consent platform appropriate to the site's regions and data uses.
Why it matters: Consent state can determine which storage and requests are permitted. Automated detection is not a legal conclusion.
How to verify: Trace baseline, reject and accept sessions in fresh browser contexts.
No page title was found in the sampled HTML.
Suggested fix: Write a unique, descriptive title that matches the page purpose.
Why it matters: Page title helps people and search systems understand the page before visiting.
How to verify: Inspect the rendered head and a search preview.
No meta description was found in the sampled HTML.
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: 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.
The current automated score is 65 out of 100.
Suggested fix: Address the largest repeatable lab bottlenecks and retest.
Why it matters: A lab score is a controlled diagnostic snapshot, not a real-user outcome.
How to verify: Rerun with the same strategy after changes and compare the underlying audits.
Homepage returned HTTP 202
Suggested fix: Return the intended canonical content with HTTP 200.
Why it matters: A crawlable success response is the baseline for indexability.
How to verify: Repeat the same public check after the change.
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.
0 headings were found in the source HTML.
Suggested fix: Use one useful top-level heading and a logical nested hierarchy.
Why it matters: A clear top-level heading helps users and automated systems understand the page structure.
How to verify: Inspect the rendered heading outline.
Document language is missing
Suggested fix: Set a valid lang attribute on the html element.
Why it matters: Screen readers use the page language to choose pronunciation rules.
How to verify: Repeat the same public check after the change.
Document language not declared
Suggested fix: Set the html lang attribute.
Why it matters: Language metadata helps screen readers and search systems interpret content.
How to verify: Repeat the same public check after the change.
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.
The sampled HTML did not include a canonical link.
Suggested fix: Declare the preferred public URL and keep it aligned with sitemap and internal links.
Why it matters: Canonical declarations help consolidate duplicate URL signals.
How to verify: Compare the final URL, canonical and sitemap entry.
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.
1 response cookie names were inspected; 1 lacked Secure or an explicit SameSite attribute.
Suggested fix: Review every affected cookie and apply Secure, HttpOnly and SameSite according to its purpose.
Why it matters: Cookie attributes limit unintended cross-site or insecure transport behaviour.
How to verify: Inspect Set-Cookie headers in a fresh session.
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.