SCAN COMPLETE

roastweb.com

🔥 Website Scan · Score 83/100

Scanned on December 20, 2025 at 01:48 AM

Share This Roast:
83
/100

Pretty solid. Minor tweaks needed.

Load Time
7.62s
HTML Size
884KB
Scripts
0
external
Images
0
Links
0
performance
63
/100
seo
92
/100
accessibility
90
/100
bestPractices
100
/100
mobile
90
/100
security
100
/100
images
100
/100
ssl
100
/100
schema
100
/100
seoEssentials
70
/100
performanceDeep
85
/100
thirdParty
100
/100
mobileReady
100
/100
privacy
100
/100

The Roast 🔥

⏰

63/100 performance. Mediocre is not a strategy.

🏋️

7.2s to show main content? Users are leaving before they even see your page.

🌍

No CDN detected. Users in Australia are still waiting for your site to load.

📝

No H1 heading. Did you forget the most basic HTML tag?

🤖

Performance score of 63/100 is embarrassingly low for a Next.js site that should be optimized out of the box - this screams lazy development

🤖

The HTML snippet shows 15+ async script tags loading simultaneously, creating a waterfall of requests that's murdering your load times

🤖

Missing H1 tag is a basic SEO failure that undermines your otherwise decent 92/100 SEO score - you're leaving easy wins on the table

🤖

Preloading an image with fetchPriority='high' while loading 15 scripts asynchronously shows you don't understand resource prioritization

🤖

The description meta tag is cut off mid-sentence in your snippet, suggesting broken HTML structure or improper truncation

The Fix 🛠️

Optimize JavaScript delivery▶ Show how to fix
Improve server response time▶ Show how to fix
Consolidate those 15+ script chunks using Next.js's built-in code splitting and bundling - you're serving a JavaScript soup instead of a proper application▶ Show how to fix
Implement proper H1 structure immediately - add <h1>x.com Website Audit Results</h1> or similar semantic heading to fix the basic accessibility and SEO gap▶ Show how to fix
Audit and optimize your image delivery: that preloaded logo.png with two srcset sizes suggests you're not using Next.js Image component correctly - switch to next/image with proper optimization▶ Show how to fix
Reduce initial JavaScript payload by at least 50% through bundle analysis and lazy loading non-critical components - your current setup is punishing users with slow devices▶ Show how to fix
Fix the broken meta description by ensuring the full description renders properly - check for unclosed tags or improper string handling in your dynamic content▶ Show how to fix

AI Deep Analysis 🤖AI

AI Summary

This site is like a sports car with flat tires - great framework choice but executed with amateur-hour mistakes that make it perform like a 1998 Geo Metro.

Overall Quality:68/100

🔍 Key Insights

•Performance score of 63/100 is embarrassingly low for a Next.js site that should be optimized out of the box - this screams lazy development
•The HTML snippet shows 15+ async script tags loading simultaneously, creating a waterfall of requests that's murdering your load times
•Missing H1 tag is a basic SEO failure that undermines your otherwise decent 92/100 SEO score - you're leaving easy wins on the table
•Preloading an image with fetchPriority='high' while loading 15 scripts asynchronously shows you don't understand resource prioritization
•The description meta tag is cut off mid-sentence in your snippet, suggesting broken HTML structure or improper truncation

💡 AI Recommendations

1.Consolidate those 15+ script chunks using Next.js's built-in code splitting and bundling - you're serving a JavaScript soup instead of a proper application
2.Implement proper H1 structure immediately - add <h1>x.com Website Audit Results</h1> or similar semantic heading to fix the basic accessibility and SEO gap
3.Audit and optimize your image delivery: that preloaded logo.png with two srcset sizes suggests you're not using Next.js Image component correctly - switch to next/image with proper optimization
4.Reduce initial JavaScript payload by at least 50% through bundle analysis and lazy loading non-critical components - your current setup is punishing users with slow devices
5.Fix the broken meta description by ensuring the full description renders properly - check for unclosed tags or improper string handling in your dynamic content
Generated by DeepSeek AI • Extended reasoning mode

Tech Stack 💻

Framework
Next.js
Server
railway-edge

Security Analysis 🔒

Security Grade
A
Security Score
100/100

Social Media 📱

Social Sharing Score
100/100
Status
✅ Good
✅
OG Title
✅
OG Description
✅
OG Image
✅
Twitter Card

Image Optimization 🖼️

Total Images
1
Missing Alt
0
Unoptimized
2
Score
100/100
WebP
0
PNG
1
JPG
0
GIF
0
SVG
0
Other
0

SSL/TLS Security 🔐

HTTPS
✅
Mixed Content
✅
HTTP Redirect
✅
Grade
A

SEO Essentials 🎯

✅
Sitemap
✅
Robots.txt
✅
Canonical
✅
Meta Desc
Title Length
47 chars
H1 Count
0
SEO Score
70/100

Structured Data 📊

Has Schema
✅
Items Found
3
Score
100/100
Types:
OrganizationWebSiteSoftwareApplication

Performance Deep Dive ⚡

Compression
gzip
Caching
✅
Total Resources
19
Score
85/100
Scripts: 17 | Styles: 1 | Images: 1

Third-Party Scripts 📦

Total Scripts
0
Tracking
0
Score
100/100

Mobile Responsiveness 📱

Viewport Tag
✅
Responsive
✅
Touch Friendly
✅
Score
100/100

Privacy & GDPR 🛡️

Cookie Notice
❌
Privacy Policy
✅
Cookie Scripts
0
Compliance Score
100/100

THINK YOUR SITE IS BETTER?

Get your free brutal audit in 10 seconds

Join 10,000+ developers who've been roasted

🔥 ROAST MY SITE
Powered by ROASTWEB