Bunshun.jp - SEO Checker - Website Review

Your Website Score is

Similar Ranking

DOW JONES – BUSINESS & FINANCIAL NEWS, ANALYSIS & INSIGHT

dowjones.com

THE OFFICIAL HOME OF YIFY MOVIES--- DOWNLOAD - YTS

yts.lt

GIBRALTAR CHRONICLE

chronicle.gi

UI KITS, ICONS, TEMPLATES, THEMES AND MORE - UPLABS

uplabs.com

NOTICIAS, DEPORTES Y ESPECTÁ--- DE GUATEMALA Y EL MUNDO | PUBLINEWS

publinews.gt

PAYSCALE - SALARY COMPARISON, SALARY SURVEY, SEARCH WAGES

payscale.com

PÁGINAS - INICIO

isciii.es

Latest Sites

FINYA LIMITED

finyalimited.com

CADOCINVESTMENT.COM | AUSTRALIAN INVESTMENT COMPANY

cadocinvestment.com

NGF LEGAL – CORPORATE LAWYER AGENCY

ngflegal.com

GLOBAL LOGISTICS AUSTRALIA | GLOBAL LOGISTICS LIMITED

globallogisticslimited.com

SHARKLEAD

platform.sharklead.network

THE GUY R COOK REPORT BLOG

guyrcook.com

CLOKIDS

clokids.shop

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

58 bunshun.jp Last Updated: 12 months

Success 78% of passed verification steps

Warning 7% of total warning

Errors 15% of total errors, require fast action

Mobile

Performance Desktop Score 26%

Best Practices Desktop Score 62%

SEO Desktop Score 90%

Progressive Web App Desktop Score 31%

Performance Mobile Score 15%

Best Practices Mobile Score 62%

SEO Mobile Score 92%

Progressive Web App Mobile Score 33%

Page Authority Authority 54%

Domain Authority Domain Authority 77%

Moz Rank 5.4/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 26 Characters

文春オンライン | 世の中の「ほんとう」がわかります

Meta Description 70 Characters

文藝春秋が運営するニュースサイト。文春オンラインは世の中を驚かせるスクープから、毎日の仕事や生活に役立つ話題までお届けする情報メディアです。

Effective URL 18 Characters

https://bunshun.jp

Excerpt Page content

文春オンライン | 世の中の「ほんとう」がわかります新着ランキングカテゴリ特集連載週刊文春文藝春秋読書コミック文春野球 ...

Keywords Cloud Density

scoop23 週刊文春10 プレゼント7 週刊文春デジタル6 この特集を見る6 アンケート5 5時間前5 文春オンライン4 文藝春秋4 お知らせ4

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
scoop	23
週刊文春	10
プレゼント	7
週刊文春デジタル	6
この特集を見る	6
アンケート	5
5時間前	5
文春オンライン	4
文藝春秋	4
お知らせ	4

Google Preview Your look like this in google search result

文春オンライン | 世の中の「ほんとう」がわかります

https://bunshun.jp

Robots.txt File Detected

http://bunshun.jp/robots.txt

Sitemap.xml File Detected

http://bunshun.jp/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~127.1 KB

Code Size: ~86.62 KB

Text Size: ~40.48 KB Ratio: 31.85%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Avoid enormous network payloads Total size was 10,926 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 5.8 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 1.0 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 22 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

Avoid an excessive DOM size 1,345 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

Minify JavaScript Potential savings of 6 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 7.6 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 489 requests • 15,073 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 191 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 150 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 8.7 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 50.0 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 30 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

Minify CSS Potential savings of 7 KB

Minifying CSS files can reduce network payload sizes

Remove unused CSS Potential savings of 49 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 702 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

User Timing marks and measures 2 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Reduce server response times (TTFB) Root document took 810 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 480 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 391 KB

Optimized images load faster and consume less cellular data

Enable text compression Potential savings of 4 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Minimize third-party usage Third-party code blocked the main thread for 210 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 310 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 2.0 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Defer offscreen images Potential savings of 1,576 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Properly size images Potential savings of 1,001 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 3.6 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 7.6 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Mobile

$Mobile Screenshot$

Serve images in next-gen formats Potential savings of 367 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

User Timing marks and measures 11 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Reduce server response times (TTFB) Root document took 810 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 2,240 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 185 KB

Optimized images load faster and consume less cellular data

Enable text compression Potential savings of 5 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Reduce the impact of third-party code Third-party code blocked the main thread for 420 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 700 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 6.6 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Defer offscreen images Potential savings of 1,270 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Properly size images Potential savings of 191 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 12.2 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 16.6 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 8,444 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 13.9 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 4.0 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 21 chains found

Avoid an excessive DOM size 1,155 elements

Minify JavaScript Potential savings of 3 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 4.0 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 478 requests • 8,444 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 161 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 190 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 22.9 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive at 22.9 s

A fast page load over a cellular network ensures a good mobile user experience

First Contentful Paint (3G) 8078 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Estimated Input Latency 50 ms

Minify CSS Potential savings of 5 KB

Minifying CSS files can reduce network payload sizes

Tap targets are sized appropriately 100% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document uses legible font sizes 83.18% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Remove unused CSS Potential savings of 27 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=0, private, must-revalidate
X-XSS-Protection: 1; mode=block
X-Request-Id: f49fddae-1a34-4b8e-9d2a-403dcdb00d0f
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Date: Thu, 28 Nov 2019 02:28:17 GMT
X-Cache: MISS
Accept-Ranges: bytes
Connection: keep-alive
Vary: Accept-Encoding,User-Agent,Cookie
Strict-Transport-Security: max-age=31536000

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	bunshun.jp	202.238.151.148	IN	6433
NS	bunshun.jp	ns00.vips.ne.jp	IN	6521
NS	bunshun.jp	nfmail.bunshun.co.jp	IN	6521
NS	bunshun.jp	ns01.vips.ne.jp	IN	6521
MX	bunshun.jp	sbmail.bunshun.co.jp	IN	6522
MX	bunshun.jp	sgw.bunshun.co.jp	IN	6522
TXT	bunshun.jp	v=spf1 +ip4:202.33.131.64/26 +ip4:180.8.39.96/29 +ip4:203.137.55.248/32 +ip4:203.137.55.249/32 +ip4:210.226.38.65/32 +ip4:210.226.38.66/32 include:crmstyle.com include:_spf.google.com ~all	IN	6522
TXT	bunshun.jp	facebook-domain-verification=pnugh9jii19d3xo5dpu4ab4s2m0nsv	IN	6522

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

58 bunshun.jp Last Updated: 12 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Clipboard js

DoubleClick for Publishers (DFP)

Google Tag Manager

jQuery

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments