Tools & Wizards About Us

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

longtalker.net

携帯電話やスマホから国際電話は格安国際電話サーチ

Page Load Speed

3.9 sec in total

First Response

552 ms

Resources Loaded

3.2 sec

Page Rendered

184 ms

About Website

Click here to check amazing Longtalker content for Japan. Otherwise, check out these important facts you probably never knew about longtalker.net

ケータイやiPhoneやスマホ(スマートフォン)から10社の格安国際電話を徹底比較。はじめて携帯電話やスマホから国際電話をかける方もカンタンに使えるリチャージ式国際電話カードを送料無料で販売中。

Visit longtalker.net

Key Findings

We analyzed Longtalker.net page load time and found that the first response time was 552 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

longtalker.net performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value2,000 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

longtalker.net

552 ms

www.longtalker.net

716 ms

style.css

163 ms

jquery.min.js

6 ms

accordion.js

324 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 50% of them (40 requests) were addressed to the original Longtalker.net, 10% (8 requests) were made to Pagead2.googlesyndication.com and 10% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Longtalker.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.9 kB (23%)

Content Size

821.4 kB

After Optimization

632.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Longtalker.net main page is 821.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 574.4 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 22.9 kB

  • Original 31.3 kB
  • After minification 31.1 kB
  • After compression 8.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.9 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 444 B

  • Original 202.4 kB
  • After minification 201.9 kB

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. Longtalker images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 154.4 kB

  • Original 574.4 kB
  • After minification 573.5 kB
  • After compression 420.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 154.4 kB or 27% of the original size.

CSS Optimization

-83%

Potential reduce by 11.1 kB

  • Original 13.3 kB
  • After minification 10.1 kB
  • After compression 2.2 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. Longtalker.net needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (53%)

Requests Now

75

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

longtalker.net accessibility score

97

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

Best Practices

longtalker.net best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

longtalker.net SEO score

77

Search Engine Optimization Advices

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

Open Graph description is not detected on the main page of Longtalker. 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: