Skip to content

Changes

https://strictmx.com
Compared to previous audit · 2 hours ago View previous audit
3
New issues
6
Resolved
8
score changes
CategoryPreviousCurrentChange
CompositeA (93)A (93)—
PerformanceA (96)A (96)—
SecurityA (96)A (96)—
AccessibilityB (86)A (90) +4.000
SEOA+ (100)A+ (100)—
InfrastructureA (92)A (92)—
ComplianceC (70)C (70)—
ContentA+ (100)A+ (100)—
SustainabilityA (95)A (95)—
MetricPreviousCurrentChange
Performance 1000010000—
Accessibility 91009100—
Best Practices 1000010000—
SEO 92009200—
PWA 00—
Desktop Performance 1000010000—
Desktop Accessibility 91009100—
Desktop Best Practices 1000010000—
Desktop SEO 92009200—
FCP 990 ms989 ms—
LCP 1.22 s1.21 s—
TBT 33 ms36 ms +3 ms
CLS 0.0100.010—
Desktop FCP 330 ms337 ms +7 ms
Desktop LCP 369 ms371 ms—
Desktop TBT 0 ms0 ms—
Desktop CLS 0.0080.008—
TTFB †304 ms545 ms +240 ms
DNS †32 ms24 ms -8 ms
TLS †96 ms183 ms +87 ms
Connect †86 ms160 ms +74 ms
Total †305 ms545 ms +240 ms

† Timing metrics may vary by worker location and do not necessarily indicate site changes.

WARNING HTTP→HTTPS redirect uses 302 instead of 301 infrastructure
WARNING https://strictmx.com/: 489ms CPU time performance
WARNING Unattributable: 348ms CPU time performance
WARNING Skip navigation link is missing (WCAG 2.4.1) accessibility
WARNING No favicon.ico at site root accessibility
WARNING https://strictmx.com/: 606ms CPU time performance
WARNING HTTP→HTTPS redirect is not permanent infrastructure
WARNING 1 field(s) would benefit from inputmode attribute accessibility
WARNING Unattributable: 365ms CPU time performance
WARNING Registrar lock is NOT enabled infrastructure
WARNING No accessibility statement detected compliance
WARNING GDPR Article 13 disclosure coverage: 2 / 8 categories compliance
WARNING Terms of Service not detected compliance

HTTP headers unchanged

13 headers unchanged

Technology stack unchanged

5 technologies unchanged

Looking ahead

+3 pts
A (93) Could reach A (96)
Compliance +10Infrastructure +8Performance +4

Estimate — actual results may vary (7 issues to fix)

Website improvement report — Strictmx

August 19, 2026 → August 19, 2026

A A 93 → 93 0 pts

6

Resolved

3

New issues

4

Still remaining

Financial summary

Investment delivered

€100 in development time

Investment remaining

€567 to complete the remaining items

Ongoing risk

€0/month in ongoing exposure

Figures are estimates based on local developer hourly rate, industry CPC, and regulatory fine ranges.

Performance by category

MetricBeforeAfterChange
Overall score93 (A)93 (A)0
Performance96 (A)96 (A)0
Security96 (A)96 (A)0
Accessibility86 (B)90 (A)+4
SEO100 (A+)100 (A+)0
Infrastructure92 (A)92 (A)0
Compliance70 (C)70 (C)0
Content100 (A+)100 (A+)0
Sustainability95 (A)95 (A)0

Resolved (6)

  • Skip navigation link is missing (WCAG 2.4.1) (Accessibility)

    → Improved usability for assistive technology users

  • No favicon.ico at site root (Accessibility)

    → Improved usability for assistive technology users

  • https://strictmx.com/: 606ms CPU time (Performance)

    → Page loads faster for users

  • HTTP→HTTPS redirect is not permanent (Infrastructure)

    → More reliable delivery

  • 1 field(s) would benefit from inputmode attribute (Accessibility)

    → Improved usability for assistive technology users

  • Unattributable: 365ms CPU time (Performance)

    → Page loads faster for users

Recommended next steps (7)

  • Sprint 3

    HTTP→HTTPS redirect uses 302 instead of 301 (Infrastructure)

  • Sprint 1

    https://strictmx.com/: 489ms CPU time (Performance)

  • Sprint 1

    Unattributable: 348ms CPU time (Performance)

  • Sprint 1

    Registrar lock is NOT enabled (Infrastructure)

  • Sprint 1

    No accessibility statement detected (Compliance)

  • Sprint 2

    GDPR Article 13 disclosure coverage: 2 / 8 categories (Compliance)

  • Sprint 1

    Terms of Service not detected (Compliance)

Send Feedback