Tools & Wizards About Us
e-kantei.net screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 0

    Accessibility

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

e-kantei.net

電話占いカリス｜当たると口コミで評判の電話占い｜占い師に今すぐ相談

Page Load Speed

16 sec in total

First Response

1.5 sec

Resources Loaded

14 sec

Page Rendered

534 ms

e-kantei.net screenshot

About Website

Visit e-kantei.net now to see the best up-to-date E Kantei content for Japan and also check out these interesting facts you probably never knew about e-kantei.net

電話占いカリスはテレビや雑誌でも取り上げられ、とにかく当たると口コミで話題。《新規登録2,600円無料》なので安心してお試しいただけます。恋人の気持ちや復縁の可能性、複雑愛から未来の行方など、全国から集まった《当たる》人気電話占い師が24時間受付中で相談可能。

Visit e-kantei.net

Key Findings

We analyzed E-kantei.net page load time and found that the first response time was 1.5 sec and then it took 14.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

e-kantei.net performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.2 s

26/100

10%

Network Requests Diagram

e-kantei.net

1512 ms

normalize.css

478 ms

slider-pro.min.css

855 ms

main.css

1885 ms

font-awesome.min.css

51 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 86% of them (68 requests) were addressed to the original E-kantei.net, 3% (2 requests) were made to Maxcdn.bootstrapcdn.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain E-kantei.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 299.3 kB (21%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-kantei.net main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 25.7 kB

  • Original 34.3 kB
  • After minification 30.6 kB
  • After compression 8.6 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 3.8 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.7 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 67.8 kB

  • Original 1.1 MB
  • After minification 1.0 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. E Kantei images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 133.4 kB

  • Original 230.4 kB
  • After minification 228.9 kB
  • After compression 97.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 133.4 kB or 58% of the original size.

CSS Optimization

-82%

Potential reduce by 72.3 kB

  • Original 88.3 kB
  • After minification 82.4 kB
  • After compression 16.0 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. E-kantei.net needs all CSS files to be minified and compressed as it can save up to 72.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (35%)

Requests Now

75

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Kantei. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

e-kantei.net

e-kantei.net

1512 ms

normalize.css

normalize.css

478 ms

slider-pro.min.css

slider-pro.min.css

855 ms

main.css

main.css

1885 ms

font-awesome.min.css

font-awesome.min.css

51 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

893 ms

conversion.js

conversion.js

62 ms

wow.min.js

wow.min.js

521 ms

jquery.min.js

jquery.min.js

95 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

546 ms

jquery.sliderPro.min.js

jquery.sliderPro.min.js

2014 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

1667 ms

rollover.js

rollover.js

1066 ms

main.js

main.js

1321 ms

analytics.js

analytics.js

160 ms

header-bg.png

header-bg.png

186 ms

header-short-shadow.png

header-short-shadow.png

490 ms

logo.png

logo.png

556 ms

header-copy.png

header-copy.png

566 ms

header-campaign.jpg

header-campaign.jpg

1135 ms

header-support.jpg

header-support.jpg

577 ms

header-tel.jpg

header-tel.jpg

710 ms

header-mail.png

header-mail.png

1036 ms

global-guest.jpg

global-guest.jpg

2355 ms

slider-4.jpg

slider-4.jpg

3661 ms

slider-1.jpg

slider-1.jpg

2260 ms

slider-3.jpg

slider-3.jpg

5537 ms

main-bg.jpg

main-bg.jpg

1537 ms

main-flower-bg.png

main-flower-bg.png

2461 ms

concept-bg.png

concept-bg.png

3340 ms

concept.png

concept.png

3147 ms

read-concept.png

read-concept.png

2823 ms

new-arrival-title-en.png

new-arrival-title-en.png

2970 ms

new-arrival-title.png

new-arrival-title.png

3684 ms

new-flag.png

new-flag.png

3493 ms

icons.png

icons.png

3677 ms

1_m.jpg

1_m.jpg

4203 ms

1_m.jpg

1_m.jpg

3994 ms

1_m.jpg

1_m.jpg

4484 ms

1_m.jpg

1_m.jpg

4551 ms

1_m.jpg

1_m.jpg

4598 ms

1_m.jpg

1_m.jpg

4498 ms

1_m.jpg

1_m.jpg

5030 ms

1_m.jpg

1_m.jpg

4981 ms

carousel-prev.png

carousel-prev.png

5065 ms

caorusel-next.png

caorusel-next.png

5067 ms

list-title-en.png

list-title-en.png

5117 ms

list-title.png

list-title.png

5815 ms

current-shadow.jpg

current-shadow.jpg

5555 ms

content-sub-bg.png

content-sub-bg.png

5479 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

44 ms

sidebar-bg.jpg

sidebar-bg.jpg

5509 ms

76 ms

fbds.js

fbds.js

112 ms

collect

collect

26 ms

49 ms

dividr.png

dividr.png

5504 ms

collect

collect

67 ms

102 ms

regist-btn.png

regist-btn.png

5543 ms

login-head.jpg

login-head.jpg

5863 ms

login-btn.png

login-btn.png

5521 ms

search-head.jpg

search-head.jpg

5582 ms

about-head.jpg

about-head.jpg

5533 ms

category-btn.jpg

category-btn.jpg

5286 ms

arrow-red.png

arrow-red.png

5423 ms

method-head.jpg

method-head.jpg

5063 ms

mobile-head.png

mobile-head.png

4384 ms

qr.png

qr.png

4398 ms

to-top.png

to-top.png

4359 ms

footer-logo-line.png

footer-logo-line.png

4096 ms

logo-white.png

logo-white.png

4141 ms

arrow-white-small.png

arrow-white-small.png

3972 ms

ga.php

ga.php

4031 ms

logo-small.png

logo-small.png

195 ms

openhand.cur

openhand.cur

173 ms

nav-left.png

nav-left.png

474 ms

nav-right.png

nav-right.png

511 ms

regist-btn_o.png

regist-btn_o.png

528 ms

Best Practices

e-kantei.net best practices score

77

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

e-kantei.net SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-kantei.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that E-kantei.net main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

e-kantei.net

Open Graph description is not detected on the main page of E Kantei. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: