What does StackOptic analyze?

StackOptic runs 18 analysis modules on any public website from a single URL. It detects 7,000+ technologies (CMS, frameworks, analytics, payments, CDN, hosting), evaluates SSL certificates and HTTP security headers with grades from A+ to F, measures Core Web Vitals (LCP, CLS, TBT, FCP), audits SEO meta tags and structured data, checks email security (SPF, DKIM, DMARC), analyzes AI & LLM readiness including bot access and llms.txt validation, extracts color palettes and typography, estimates carbon footprint, and generates permanent shareable reports.

Does it work on sites behind Cloudflare or bot protection?

Yes. StackOptic uses a real browser engine that loads pages exactly like a human visitor — executing JavaScript, rendering CSS, and handling redirects. This allows it to bypass Cloudflare, LiteSpeed, Sucuri, and other bot protection systems where traditional crawlers and HTTP-only tools fail.

What do I get on the free plan?

The free plan includes 5 analyses per day with access to all 18 modules, full scores, technology detection, and security grades. Every report is permanently accessible via a unique shareable URL — no login required to view. No credit card needed. AI-powered insights, re-analysis, PDF/JSON export, and comparison features are available on Pro ($24/mo) and Agency ($99/mo) plans.

What is AI & LLM readiness analysis?

This module evaluates how visible and citable your website is to AI search engines like ChatGPT, Perplexity, Google AI Overviews, and Claude. It audits access permissions for 8 major AI bots, validates llms.txt and llms-full.txt files, scores citation-ready content structure, and analyzes structured data (JSON-LD) for GEO readiness — helping you rank in the next generation of search.

How long does an analysis take?

Most analyses complete in under 10 seconds. StackOptic runs all 18 modules in parallel using a real browser session, so you get technology detection, security audit, performance metrics, SEO analysis, and AI readiness scoring simultaneously.

How accurate are the results?

Detection is based on real browser execution — DOM inspection, JavaScript runtime analysis, HTTP headers, and DNS records. With 7,000+ technology signatures and Lighthouse-calibrated performance scoring, StackOptic achieves high accuracy for mainstream technologies.

What security checks are performed?

The security module evaluates SSL/TLS certificates, 12+ HTTP security headers (HSTS, CSP, X-Frame-Options, Permissions-Policy, Referrer-Policy), HTTPS enforcement, and email authentication (SPF, DKIM, DMARC). Each site receives a letter grade from A+ to F with specific remediation steps.

Do you store the websites I analyze?

StackOptic only stores publicly available information that any visitor to a website would see — HTML content, HTTP headers, DNS records, and screenshots. We do not access private data, log in to websites, or perform any intrusive testing.

Back to Search

paypay.ne.jp

https://paypay.ne.jp· First analyzed 23 Apr 2026· Updated 23 Apr 2026

Export

paypay.ne.jp

Mobile

Sponsored

Hosting Provider

Amazon Web Services (AWS)

aws.amazon.com

IP Address

3.164.206.22

Site Location

🇯🇵 Japanvia tld

Server Location

🇫🇮 Helsinki, Finland

ASN

AS16509

Organization

AWS CloudFront (GLOBAL)

Server

Nginx

CDN

CloudFront

Nameservers

ns-138.awsdns-17.com.ns-1549.awsdns-01.co.uk.ns-900.awsdns-48.net.ns-1066.awsdns-05.org.

Performance

Core Web Vitals

Weight

First Contentful Paint

777 ms10%

Speed Index

1.0 s10%

Largest Contentful Paint

—25%

Total Blocking Time

0.0 ms30%

Cumulative Layout Shift

0.00025%

546 KB

74 requests

Image Optimization

Lazy Load

0–49

50–89

90–100

Architecture Stack

Monolithic

⚙️ SSR

WordPressv6.8.1

cms

paypay.co.jpv1.0.5Custom

by Author URI:

Technology Stack

10 Technologies Detected

Analytics

Plugins

Libraries

UI Components

CSS Frameworks

Fonts

Tag Managers

Web Servers

SEO Analysis

B71/100

Meta Tags10/15

Content9/12

Headings8/8

Technical23/25

E-E-A-T0/7

Images1/7

Links4/5

URL5/5

Social4/5

Freshness0/4

Mobile4/4

Indexability3/3

paypay.ne.jppaypay.ne.jp

PayPay（ペイペイ）- QRコードで支払うキャッシュレス決済のスマホアプリ

PayPayは、スマホひとつでカンタン・おトクにお支払いができるアプリです。最短1分で登録完了！街のお店をはじめ、ネットサービスや請求書のお支払いなどにもご使用いただけます。

Title Length39 chars

Recommended: 50-60 chars (~244px / 580px)

Description Length87 chars

Recommended: 120-160 chars

Issues (1)

• Most images missing alt text (39/72) — critical for accessibility and SEO

6 issues found

Upgrade to view details

Crawlability

Sitemap

Type: index

44 URLs

44 sub-sitemaps

robots.txt

15 rules

Sitemap reference found

Local SEO

Local Search Readiness

10/100

Poor

3 13 1

This site doesn't appear to be a local business. Local SEO signals are optional for non-local websites.

Sponsored

AI & LLM Readiness

F39/100

Bot Access

20/25

Machine Read.

7/25

Schema Data

4/25

Citation

8/25

AI Bot Access

14/14 accessible

AI Search

OAI-SearchBot

PerplexityBot

Claude-SearchBot

Gemini-Deep-Research

DuckAssistBot

Training

GPTBot

ClaudeBot

Google-Extended

Meta-ExternalAgent

Bytespiderinfo

Amazonbot

Applebot-Extended

CCBotinfo

Fetch

ChatGPT-User

Machine Readability

llms.txt

llms-full.txt

Semantic HTML

Heading Hierarchy

header/footer

Text ratio:4%

Words:250

Token eff.:Too Short

Sections/1K:92

Depth:1/5

Structured Data

3 JSON-LD

WebSiteBreadcrumbListSearchAction

Citation Readiness

Opening Summary

Descriptive Headingsavg 1w

Canonical URL

Open Graph3/3

Twitter Card1/3

Language Tag

Publish Date

Author Info

Lists

Tables

TL;DR / Summary

About Page Link

Recommendations (10)

AI readiness recommendation preview...

Upgrade to view recommendations

Sponsored

Accessibility

WCAG 2.1 Compliance

Evaluates how accessible your website is for users with disabilities, based on WCAG 2.1 guidelines. Checks images, forms, keyboard navigation, ARIA roles, and color contrast.

77/100

Passed

Critical

Warnings

Images & Alt Text

20/20

Checks if images have descriptive alt text for screen readers and visually impaired users.

Semantic Structure

18/20

Evaluates proper use of HTML5 semantic elements (header, nav, main, footer) and heading hierarchy.

Forms & Inputs

15/15

Verifies form fields have labels, error messages are clear, and inputs are properly associated.

Color & Contrast

15/15

Tests text-to-background color contrast ratios against WCAG AA/AAA minimum requirements.

Keyboard & Focus

9/15

Ensures all interactive elements are reachable and operable via keyboard (tab, enter, escape).

ARIA & Roles

0/15

Checks correct use of WAI-ARIA attributes (roles, states, properties) for assistive technologies.

2 recommendations

•Accessibility recommendation preview...

Upgrade to view recommendations

Carbon Footprint

SWDM v4 · Eco-Score

Carbon emissions estimated using the Sustainable Web Design Model v4 (SWDM v4). Factors in data center, network, and device energy across new and returning visitors. Grade thresholds based on HTTP Archive percentiles.

64/100

55 mg

CO₂e / view

545.8 KB

Page Weight

80%

Cleaner Than

New Visitor

63 mg

Returning (cached)

32 mg

Annual (10K/mo)

6.6 kg

Emission Segments

Data Center

3 mg

Network

16 mg

Device

36 mg

Resource Breakdown

JavaScript

55.3 KB

Images

319.9 KB

CSS

96.0 KB

Fonts

59.5 KB

HTML

15.2 KB

Green Hosting Verified

Amazon Web Services (AWS)

Provider Match

4 recommendations

•Carbon footprint recommendation preview...

Upgrade to view recommendations

Security Score

86%Very Good

Static / Informational

HTTPS

No WAF

220d

Certificate Details

Type

Organization Validated (OV)

Certificate Authority

GlobalSign nv-sa

Key Algorithm

RSA (2048 bit)

Signature

SHA-256 with RSA

TLS Version

TLSv1.3

HTTP Protocol

HTTP/2+H3

Valid From

29.10.2025

Valid Until

30.11.2026

OCSP Stapling

Enabled

Subject Alternative Names (2)

*.paypay.ne.jppaypay.ne.jp

SHA-256 Fingerprint

51:56:92:20:41:08:E0:C0:84:A2:F5:11:DF:53:01:BA:DF:2D:20:70...

Recommendations

Security recommendation preview

Upgrade to view recommendations

Upgrade to view header details

HTTP Headers

Developer Console

age

840

alt-svc

h3=":443"; ma=86400

content-encoding

📦 Gzip(gzip)

content-security-policy

default-src 'self' 'unsafe-inline' 'unsafe-eval' data: https...

content-type

text/html; charset=UTF-8

date

Thu, 23 Apr 2026 19:04:38 GMT

Good Warning Issue

Email Infrastructure

Google Workspace

Score

SPF

DKIM

DMARC

DMARC Policy

Quarantine (Moderate)

MX Records (5)

alt3.aspmx.l.google.com

alt1.aspmx.l.google.com

alt4.aspmx.l.google.com

alt2.aspmx.l.google.com

+1 more

Domain Information

paypay.ne.jp

DNSSEC

Not Enabled

Privacy & Compliance

OneTrust

Cookie Consent Banner

OneTrust

GDPR Indicators

Cookie consent banner detected

CMP: OneTrust

Mobile Compatibility

Viewport & Responsive Test

Tests how well your website works on mobile devices. Checks viewport configuration, responsive layout, touch targets, font readability, and simulates rendering across different screen sizes.

62/100

Mobile Friendly2 breakpoints

Viewport Meta

The viewport meta tag tells mobile browsers how to scale the page. Without it, mobile devices render at desktop width.

Responsive Design

Uses CSS media queries or flexible layouts to adapt content to different screen sizes automatically.

Touch Icons

Apple touch icons and favicons displayed when users add the site to their home screen on mobile devices.

Readable Font Size

Base font size should be at least 16px on mobile to ensure text is readable without zooming.

Relative Units

Using em, rem, %, or vw instead of fixed px values allows content to scale properly across screen sizes.

No H-Scroll Risk

No elements wider than the viewport that would cause horizontal scrolling on mobile devices.

Tap Targets OK

Interactive elements (buttons, links) are at least 48x48px with enough spacing to prevent accidental taps.

No Fixed Widths

No elements with fixed pixel widths that could overflow on smaller screens and break the layout.

Viewport

initial-scale=1.0

1 recommendation

•Mobile compatibility recommendation preview...

Upgrade to view recommendations

Typography & Readability

Hiragino Kaku Gothic ProN

WCAG Partial

62/100

Readability

/30

19/30

16px · LH 1.70

Hierarchy

/20

18/20

3.44x ratio · ✓ H1→H6

WCAG

/25

10/25

1:1 min contrast

Performance

/25

15/25

2 fonts · 1 req

Heading Font

Hiragino Kaku Gothic ProN

Sans55px

Body Font

Hiragino Kaku Gothic ProN

Sans16px

Contrast Ratio

1:1

4 issues

Reading Comfort

~40 CPL

Narrow lines

55px

42px

35px

16px

✅ Excellent readability: 16px body text is ideal for all devices.

⚠️ Hard to read: Flesch score 46/100. Simplify sentences for wider reach.

⚠️ Partial contrast: 4 elements below WCAG AA threshold (min 1.0:1).

✅ Perfect heading hierarchy: Sequential h1→h2→h3 with single H1 — ideal for SEO & accessibility.

✅ Strong hierarchy: Headlines are 3.4x larger than body text.

❌ Pure vw font sizes: Viewport units alone break browser zoom (WCAG 1.4.4 fail). Use clamp(rem, vw, rem).

GGoogle Fonts Buy on MyFontsFlesch 47

Color Palette

8 unique colors

3.51:1 AA Large Light

#ffffff

Background· 26.6%

#808b8a

Other· 6%

#785553

Primary· 6.8%

#211f27

Text· 5.2%

#a59189

Secondary· 4.5%

Business & Marketing Stack

2 Tools Detected

Growing

Behavior Analytics

Google Tag ManagerFree

Google AnalyticsFree

User behavior and product analytics

Sponsored

Scripts & Styles

26 Resources

Scripts

Styles

Async

Defer

Top Script Sources

paypay.ne.jp(10)googletagmanager.com(3)j.wovn.io(1)js.ptengine.jp(1)cdn-au.onetrust.com(1)

Website Identity

PayPay（ペイペイ）- QRコードで支払うキャッシュレス決済のスマホアプリ

paypay.ne.jp/

Location detected: 🇯🇵 Japanvia tld

📧 Google Workspaceja

Social Profiles

Facebook X (Twitter)Instagram YouTube

Sponsored

Last analyzed: 23 Apr 2026 at 19:18

Historical Analysis & Change Tracking