Coocan.jp - SEO Checker - Website Review

Your Website Score is

Similar Ranking

質問・疑問に答えるQ&AサイトOKWAVE

okwave.jp

МУЖСКОЙ ЖУРНАЛ MAXIM ONLINE. ОФИЦИАЛЬНЫЙ САЙТ ЛУЧШЕГО МУЖСКОГО ЖУРНАЛА MAXIM.

maximonline.ru

LAMIAREPORT.GR

lamiareport.gr

delta-search.com

MY.COM — COMMUNICATION AND ENTERTAINMENT SERVICES: MYMAIL, MAPS.ME, AND GAMES.

my.com

HABER ZAMANI | HABERLER ZAMANINDA OKUNUR

haberzamani.com

魅族官网 - 魅族 16XS 手机,极边全面屏三摄长续航

meizu.com

Latest Sites

ACUITY FUNDING

acuityfunding.com

sharenow126.com

MASUK

gm066.com

恭喜，站点创建成功！

51278.cc

m.fun8899jk.com

JOBIFY

jobify2u.com

PROLIKE

prolikeid.com

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

2 coocan.jp Last Updated: 1 year

Success 24% of passed verification steps

Warning 38% of total warning

Errors 38% of total errors, require fast action

Mobile

Performance Desktop Score 98%

Best Practices Desktop Score 62%

SEO Desktop Score 89%

Progressive Web App Desktop Score 31%

Performance Mobile Score 93%

Best Practices Mobile Score 62%

SEO Mobile Score 73%

Progressive Web App Mobile Score 30%

Page Authority Authority 0%

Domain Authority Domain Authority 0%

Moz Rank 0.0/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 47 Characters

@NIFTYホームページサービス - ホームページ作成なら@NIFTYホームページサービスで！

Meta Description 0 Characters

NO DATA

Effective URL 16 Characters

http://coocan.jp

Excerpt Page content

@niftyホームページサービス - ホームページ作成なら@niftyホームページサービスで！移動しない場合はこちらをクリック。

Keywords Cloud Density

移動しない場合は1 をクリック1

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

Keyword	Freq	Title	Desc	Domain	H1	H2
移動しない場合は	1
をクリック	1

Google Preview Your look like this in google search result

@NIFTYホームページサービス - ホームページ作成なら@NIFTYホームページサービスで！

http://coocan.jp

@niftyホームページサービス - ホームページ作成なら@niftyホームページサービスで！移動しない場合はこちらをクリック。

Robots.txt File No Found

http://coocan.jp/robots.txt

Sitemap.xml File No Found

http://coocan.jp/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~577 B

Code Size: ~305 B

Text Size: ~272 B Ratio: 47.14%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

Nginx

Web Servers

PWA - Manifest

Manifest is not valid

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

Desktop

Minify JavaScript Potential savings of 24 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 0.2 s

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

Keep request counts low and transfer sizes small 59 requests • 452 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 50 resources found

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

Max Potential First Input Delay 30 ms

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

Time to Interactive 0.2 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

Estimated Input Latency 10 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 8 KB

Minifying CSS files can reduce network payload sizes

Remove unused CSS Potential savings of 42 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 64 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

Does not use HTTPS 56 insecure requests found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

Server response times are low (TTFB) Root document took 510 ms

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

Enable text compression Potential savings of 148 KB

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

Efficiently encode images Potential savings of 55 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 0 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 0 ms

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

JavaScript execution time 0.0 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

Speed Index 1.2 s

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

First CPU Idle 0.2 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).

Avoids enormous network payloads Total size was 452 KB

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

Minimizes main-thread work 0.3 s

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

First Contentful Paint 0.2 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 4 vulnerabilities detected

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

Avoids an excessive DOM size 185 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)

Mobile

First Meaningful Paint 3.4 s

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

Keep request counts low and transfer sizes small 59 requests • 452 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 50 resources found

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

Max Potential First Input Delay 130 ms

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

Time to Interactive 3.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

Estimated Input Latency 10 ms

First Contentful Paint (3G) 1279 ms

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

Minify CSS Potential savings of 8 KB

Minifying CSS files can reduce network payload sizes

Remove unused CSS Potential savings of 42 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 64 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

Does not use HTTPS 56 insecure requests found

Server response times are low (TTFB) Root document took 330 ms

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

Efficiently encode images Potential savings of 55 KB

Optimized images load faster and consume less cellular data

Enable text compression Potential savings of 148 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 0 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 180 ms

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

JavaScript execution time 0.2 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

Speed Index 2.5 s

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

First CPU Idle 3.4 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).

Avoids enormous network payloads Total size was 452 KB

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

Minimizes main-thread work 1.2 s

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

First Contentful Paint 0.7 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 4 vulnerabilities detected

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

Avoids an excessive DOM size 185 elements

Minify JavaScript Potential savings of 24 KB

Minifying JavaScript files can reduce payload sizes and script parse time

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
Server: nginx
Date: Sat, 14 Dec 2019 06:46:52 GMT
Content-Type: text/html
Content-Length: 479
Connection: keep-alive
Last-Modified: Mon, 04 Dec 2017 01:43:59 GMT
ETag: "1df-55f79da2571cc"
Accept-Ranges: bytes

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	coocan.jp	210.131.2.35	IN	3571
NS	coocan.jp	ons0.nifty.ad.jp	IN	62633
NS	coocan.jp	ons1.nifty.ad.jp	IN	62633

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

2 coocan.jp Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Nginx

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