Website review, no card needed
socialfansgeek.com website review
Visit site (opens in a new tab)Reviewed 26 October 202625 issues · 83 checks
This review found 25 issues worth fixing on socialfansgeek.com, 9 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 4.9 s |
| Jul 18, 2026 | 5.5 s |
| Jul 25, 2026 | 5.5 s |
| Aug 1, 2026 | 5.6 s |
| Aug 8, 2026 | 5.8 s |
| Aug 15, 2026 | 5.9 s |
| Aug 22, 2026 | 6.1 s |
| Aug 29, 2026 | 6.3 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.4 s |
| Sep 19, 2026 | 6.3 s |
| Sep 26, 2026 | 5.9 s |
| Oct 3, 2026 | 6.0 s |
| Oct 10, 2026 | 5.4 s |
| Oct 17, 2026 | 5.3 s |
| Oct 24, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 131 ms |
| May 16, 2026 | 128 ms |
| May 23, 2026 | 142 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 143 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 142 ms |
| Jul 11, 2026 | 153 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 148 ms |
| Aug 1, 2026 | 149 ms |
| Aug 8, 2026 | 133 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 159 ms |
| Sep 12, 2026 | 161 ms |
| Sep 19, 2026 | 147 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 152 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 143 ms |
| Oct 24, 2026 | 123 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.6 s
Speed
Improve image delivery
2.3 MB2 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
2.0 MB9 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).
1,761 HTML elements
The page has 1,761 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
125 KiBAbout 125 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
62 KiBAbout 62 KiB of CSS is downloaded but never applied on this page.
2 third-party services on the page
2 third-party services load with your homepage (Other Google APIs/SDKs and iconify.design), adding 120 KiB and 44 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 53 ms. During a long task the page ignores taps.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
3 checks passed
Mobile performance score: 98
98/100Your mobile performance score is 98 (desktop: 93). That is in Google's “good” band (90 and up).
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 122 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.4 s
4.4 sReal visitors see the first content after 4.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.8 s
3.8 sReal visitors wait 3.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 88% slower for real visitors
+88%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 131 ms to 123 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user INP: 123 ms
123 msReal visitors wait 123 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Time to Interactive: 3.2 s
3.2 sThe page is fully interactive after 3.2 s.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Largest Contentful Paint: 1.1 s
1.1 sYour largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “AI Marketing & Creator Infrastructure Platform”.
Total Blocking Time: 2 ms
2 msScripts block the page for only 2 ms while loading. Good is under 200 ms.
Images and page weight
2 images over 500 KB
2 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
2.1 MB2 images are downloaded at several times the size a phone draws them, for example cinematic-fan-poster.jpg at 1,536 px wide, shown at 146 px. Resized copies would save about 2.1 MB.
Page weight: 2.8 MB in 32 requests
2.8 MBYour homepage downloads 2.8 MB in 32 requests on a phone: images 2.4 MB (8), scripts 182 KiB (4) and fonts 110 KiB (5). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (2.3 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 96.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Interactive controls must not be nested (14 elements)
Interactive controls must not be nested: 14 elements on the page fail this check, rated serious by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (25 elements)
All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
53 links without text
53 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (14 elements)
Headings should not be empty: 14 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 85 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
215 internal links, 4 external
The homepage links to 215 pages on socialfansgeek.com and 4 external pages.
8 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Buy high-retention social media followers, likes, & views safely. Tap into free AI tools for instant scripts, bios, & h…”.
One H1 headline
Your main headline reads: “AI Marketing & Creator Infrastructure Platform”.
Title: 45 characters
Your title is a healthy 45 characters: “Buy Views, Likes, Engagements & Free AI Tools”.
Canonical URL set
The canonical URL is https://www.socialfansgeek.com/.
Structured data in place
Structured data found: FAQPage, HowTo, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.socialfansgeek.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 4 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (3,810 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.socialfansgeek.com/llms.txt (26 KiB, 124 links), a plain-text guide to the site for AI tools.
Other pages
2 pages slow to respond
https://www.socialfansgeek.com/marketplace and https://www.socialfansgeek.com/product/buy-facebook-reels-views took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 107 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://www.socialfansgeek.com' has be…”.
2 checks passed
Tap targets are thumb-sized
27 of 28 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 377 words of copy
The homepage carries about 377 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Signup” and “SIGN UP FREE”.
44 calls to action
The homepage has 44 calls to action, for example “Check Order Status”, “Signup” and “Buy Reddit Upvotes”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 14 testimonial or review blocks, 17 customer or partner logos and “Join 10,000+ satisfied customers”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at socialfansgeek.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on socialfansgeek.com, including 9 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.