← Back to browse

WordPressBugFix.pro

Senior WordPress developers on standby. Most bugs fixed in under 2 hours. Fair 25/75 payment split.

wordpressbugfix.pro · Added June 11, 2026 · Last analysed June 11, 2026 · via · 75% unique tagline

StackScope is a free public catalogue of indie launches. We find launches on Product Hunt, Hacker News and similar feeds, then crawl each site to detect its tech stack and score it for launch readiness: DNS, security headers, SEO basics. This page is what we saw on 11 June 2026; the live site may have changed since.

WordPressBugFix.pro is partway there, with a thorough launch checklist and clean crawl signals. Visible gaps: missing several security headers, incomplete legal pages, and analytics without a consent banner.

Launched on Product Hunt on June 11, 2026. The site is hosted on Hostinger International Limited in Germany. The crawl picked up 7 technologies on this site, covering analytics, CSS frameworks, hosting, and protocol. The stack includes Tailwind CSS, Google Analytics, and Hostinger.

For context, it's on one of the most common stacks we track, shared by 121 launches.

If you own this site, refresh the snapshot and see the full fix list any time →

Vibe Score 35 · Some AI signals
Informational pattern-match signal. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (7)

Infrastructure
Hosting Hostinger (2)
Protocol HTTP/3
Server LiteSpeed Web Server
Build & Framework
CSS framework Tailwind CSS
UI library shadcn/ui
Analytics & Marketing
Analytics Google Analytics (3)
Microsoft Clarity

Infrastructure

DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
Let's Encrypt
Valid 22 May 2026 to 20 Aug 2026
Certificate as captured in this snapshot, not a live check.

Email Security

SPF ~all Soft-fail (~all). Common and accepted.
?
DKIM Not detected at common selectors. Your provider may use a custom one.
DMARC p=none None (p=none). Monitoring only.
?
MTA-STS Not deployed. Mail to your domain can be downgraded to plaintext en route.
?
TLS-RPT Not configured. You won't hear about silent SMTP TLS handshake failures.

Storage (2)

Cookies (2)
NameLifetimeDetected as
_ga 1y Google Analytics
_ga_J8ZRSY4TC2 1y Google Analytics

Readiness Breakdown How?

Custom title and meta description
Open Graph tags (title, image, description)
Twitter card meta tags
Canonical URL declared
Responsive viewport meta tag
Favicon present
Semantic HTML (nav, main, article)
Meta description is 178 characters (advisory) Google only shows about 155–160 characters of the description in desktop search results (less on mobile); anything past that won't appear.

Performance How?

546 ms Server response
32% Faster than peers
948 ms Largest contentful paint
0.00 Cumulative layout shift
298 KB Page weight
84 KB Image weight
4 Third-party domains
0 Console errors
0 Failed requests

Indicative grade from a single automated render, not a substitute for Lighthouse or field data, and not part of the StackScope score.

Vibe Score Breakdown How?

SignalPoints
AI palette signals +5
AI writing signals +5
AI code-structure signals +5

This score is based on structural patterns and is not definitive. Many legitimate sites may trigger signals, and AI-built sites may go undetected. It should be treated as an indicator, not a verdict.

AI Stance

No AI stance declared
llms.txt published
No AI bots blocked in robots.txt
? No directive declared
? None advertised

Well-Known Files

sitemap.xml (13 URLs)
security.txt
llms.txt
ads.txt
humans.txt
? Privacy Policy not detected
? Terms of Service not detected
? Consent manager not detected
Analytics detected; tracking fires without visitor opt-in.
Detection works best on English language sites.

Security Headers (1/6)

Permissions-Policy experimental (check browser support)
X-XSS-Protection deprecated (use Content-Security-Policy)

Build

HTML minified
CSS minified
JS minified
Code splitting
4 JS files
1 CSS files
4 Third-party domains

Brand Colours

Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.