Ecnavi.jp - SEO Checker - Website Review

Your Website Score is

Similar Ranking

LUMPTY: LEARNING FOR THE FUN OF IT

lumpty.com

FREE ADVERTISING TRAFFIC EXCHANGE - TRAFFIC AD BAR

trafficadbar.com

JUST A MOMENT...

rmz.cr

WEB色見本原色大辞典 - HTMLカラーコード

colordic.org

PRESS INFORMATION BUREAU

pib.gov.in

理想生活上天猫

小谊家的小球星-HELLO, WORLD!

tiyu68.com

Latest Sites

THIẾT KẾ - THI CÔNG NỘI THẤT - SẢN XUẤT TRỰC TIẾP | NỘI THẤT MẠNH HỆ

noithatmanhhe.vn

SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP

nhacanhothongminh.com

CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM

crypto-mining.biz

99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING

999dice.com

RELANDICE BOT FOR 999DICE

relandice.com

❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !

baophong.vn

ONE MORE STEP

seeking.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

34 ecnavi.jp Last Updated: 10 months

Success 62% of passed verification steps

Warning 15% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 55%

Best Practices Desktop Score 62%

SEO Desktop Score 80%

Progressive Web App Desktop Score 19%

Performance Mobile Score 60%

Best Practices Mobile Score 69%

SEO Mobile Score 92%

Progressive Web App Mobile Score 59%

Page Authority Authority 52%

Domain Authority Domain Authority 46%

Moz Rank 5.2/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: EUC-JP

Title Tag 22 Characters

ECナビ - お小遣いを稼げるポイントサイト

Meta Description 123 Characters

ECナビは、日本最大級のポイントサイトです。ネットショッピングやアンケート、無料会員登録やミニゲームなどで現金や電子マネー、ギフト券などと交換できるポイントが貰えます。副業、副収入にも最適。毎日ポイントをゲットして、カンタンお小遣いかせぎしよう！

Effective URL 17 Characters

https://ecnavi.jp

Excerpt Page content

ECナビ - お小遣いを稼げるポイントサイト Cookieが無効になっています。ポイント獲得するには有効にしてください。 JavaScriptが無効になっています。ポイント獲得するには有効にしてください。 ECナビ毎日貯まるポイントサイト ...

Keywords Cloud Density

ポイント加算条件9 サービス4 12月09日4 モニター3 お友達紹介3 購入金額の3 12月05日3 無料会員登録3 ショッピング3 アンケート3

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

Keyword	Freq	Title	Desc	Domain	H1	H2
ポイント加算条件	9
サービス	4
12月09日	4
モニター	3
お友達紹介	3
購入金額の	3
12月05日	3
無料会員登録	3
ショッピング	3
アンケート	3

Google Preview Your look like this in google search result

ECナビ - お小遣いを稼げるポイントサイト

https://ecnavi.jp

Robots.txt File Detected

http://ecnavi.jp/robots.txt

Sitemap.xml File No Found

http://ecnavi.jp/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~119.01 KB

Code Size: ~76.2 KB

Text Size: ~42.81 KB Ratio: 35.97%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

Amazon Cloudfront

CDN

Apache

Web Servers

PWA - Manifest

Manifest is not valid

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

Desktop

User Timing marks and measures 8 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 1,720 ms

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

Eliminate render-blocking resources Potential savings of 510 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 178 KB

Optimized images load faster and consume less cellular data

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

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

JavaScript execution time 1.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 197 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 159 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 3.0 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 2,457 KB

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

Minimize main-thread work 2.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 1.1 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 3 vulnerabilities detected

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

Avoid chaining critical requests 15 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,139 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 29 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 1.2 s

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

Keep request counts low and transfer sizes small 253 requests • 2,457 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 89 resources found

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

Max Potential First Input Delay 60 ms

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

Time to Interactive 4.0 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 22.5 s

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

Estimated Input Latency 20 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

Remove unused CSS Potential savings of 138 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 567 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

Mobile

Defer offscreen images Potential savings of 21 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

Speed Index 7.1 s

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

First CPU Idle 5.0 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 764 KB

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

Minimize main-thread work 3.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 3.3 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 3 vulnerabilities detected

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

Avoid chaining critical requests 5 chains found

Avoids an excessive DOM size 142 elements

Minify JavaScript Potential savings of 27 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 3.5 s

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

Keep request counts low and transfer sizes small 36 requests • 764 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 23 resources found

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

Max Potential First Input Delay 240 ms

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

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

First Contentful Paint (3G) 6838 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

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 100% 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 94 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

Avoid multiple page redirects Potential savings of 780 ms

Redirects introduce additional delays before the page can be loaded

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

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

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

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

Enable text compression Potential savings of 211 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 510 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 260 ms

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

JavaScript execution time 1.3 s

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

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=EUC-JP
Connection: keep-alive
Date: Mon, 09 Dec 2019 12:06:10 GMT
Server: Apache
Set-Cookie: Apache=6b603a99.5994438a25003; path=/
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Last-Modified: Mon, 09 Dec 2019 12:06:10 GMT
Cache-Control: no-cache, must-revalidate
Pragma: no-cache
Content-Security-Policy-Report-Only: default-src https: ; script-src https: 'unsafe-inline' 'unsafe-eval'; style-src https: 'unsafe-inline'; img-src https: data:; report-uri /csp/
Strict-Transport-Security: max-age=31536000;
X-Cache: Miss from cloudfront
Via: 1.1 8d41af75f0c67663aa0315daec98e02c.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: EWR52-C3
X-Amz-Cf-Id: ajQmO3ZFgjQYxfSWEGiMSoskj3eWOJyFW900jXR_0U5cKQJ5DQ0b8g==

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	ecnavi.jp	99.84.40.11	IN	59
NS	ecnavi.jp	ns-1097.awsdns-09.org	IN	86324
NS	ecnavi.jp	ns-751.awsdns-29.net	IN	86324
NS	ecnavi.jp	ns-1830.awsdns-36.co.uk	IN	86324
NS	ecnavi.jp	ns-469.awsdns-58.com	IN	86324
MX	ecnavi.jp	alt1.aspmx.l.google.com	IN	900
MX	ecnavi.jp	aspmx3.googlemail.com	IN	900
MX	ecnavi.jp	aspmx.l.google.com	IN	900
MX	ecnavi.jp	aspmx2.googlemail.com	IN	900
MX	ecnavi.jp	aspmx5.googlemail.com	IN	900
MX	ecnavi.jp	aspmx4.googlemail.com	IN	900
MX	ecnavi.jp	alt2.aspmx.l.google.com	IN	900
TXT	ecnavi.jp	v=spf1 include:spf.voyagegr.info include:_spf.google.com include:voyage.maildealer.jp include:voyage.spf.cuenote.jp include:amazonses.com ~all	IN	300

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

34 ecnavi.jp Last Updated: 10 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Amazon Cloudfront

Apache

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