Tools & Wizards About Us
telecom-land.jp screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

telecom-land.jp

携帯電話 激安価格の販売ショップ 【テレウェーブ (金町・栃木) 】

Page Load Speed

7.7 sec in total

First Response

2.6 sec

Resources Loaded

4.9 sec

Page Rendered

229 ms

telecom-land.jp screenshot

About Website

Welcome to telecom-land.jp homepage info - get ready to check Telecom Land best content for Japan right away, or after learning these important things about telecom-land.jp

東京都葛飾区・栃木県栃木市の携帯電話激安販売ショップ　テレウェーブのホームページです。当店では販売価格を常に公開しお客様にご満足いただけるサイト作りを目指しております。

Visit telecom-land.jp

Key Findings

We analyzed Telecom-land.jp page load time and found that the first response time was 2.6 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

telecom-land.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value1.965

0/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

telecom-land.jp

2584 ms

reset.css

410 ms

class.css

800 ms

style.css

829 ms

menu.css

422 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 71% of them (90 requests) were addressed to the original Telecom-land.jp, 14% (18 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Biz.line.naver.jp. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Telecom-land.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 231.4 kB (24%)

Content Size

954.1 kB

After Optimization

722.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Telecom-land.jp main page is 954.1 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. Images take 736.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 61.2 kB

  • Original 74.3 kB
  • After minification 60.5 kB
  • After compression 13.0 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 13.7 kB, which is 18% 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 61.2 kB or 82% of the original size.

Image Optimization

-13%

Potential reduce by 94.9 kB

  • Original 736.3 kB
  • After minification 641.4 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. Obviously, Telecom Land needs image optimization as it can save up to 94.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-30%

Potential reduce by 23.8 kB

  • Original 78.6 kB
  • After minification 73.9 kB
  • After compression 54.8 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 23.8 kB or 30% of the original size.

CSS Optimization

-79%

Potential reduce by 51.5 kB

  • Original 64.9 kB
  • After minification 54.9 kB
  • After compression 13.4 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. Telecom-land.jp needs all CSS files to be minified and compressed as it can save up to 51.5 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (34%)

Requests Now

123

After Optimization

81

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

telecom-land.jp

telecom-land.jp

2584 ms

reset.css

reset.css

410 ms

class.css

class.css

800 ms

style.css

style.css

829 ms

menu.css

menu.css

422 ms

jquery.min.js

jquery.min.js

14 ms

share.js

share.js

625 ms

menu.js

menu.js

612 ms

widgets.js

widgets.js

51 ms

twitterWTL.js

twitterWTL.js

147 ms

top.css

top.css

852 ms

jquery.bxslider.css

jquery.bxslider.css

815 ms

jQueryAutoHeight.js

jQueryAutoHeight.js

853 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

1001 ms

fonts.google.com

fonts.google.com

117 ms

widget.js

widget.js

4 ms

tag.js

tag.js

599 ms

addfriends_ja.png

addfriends_ja.png

495 ms

bgt

bgt

1014 ms

0.gif

0.gif

706 ms

bgt

bgt

831 ms

0.gif

0.gif

678 ms

logo_line.png

logo_line.png

204 ms

logo_pc.png

logo_pc.png

215 ms

logo_sp.png

logo_sp.png

214 ms

fb_sp.png

fb_sp.png

215 ms

twitter_sp.png

twitter_sp.png

204 ms

line_sp.png

line_sp.png

410 ms

dot_back.png

dot_back.png

408 ms

header_access.png

header_access.png

424 ms

diagonal_back.png

diagonal_back.png

424 ms

diagonal_sankaku.png

diagonal_sankaku.png

426 ms

nav_back.png

nav_back.png

610 ms

nav_home.png

nav_home.png

611 ms

nav_price.png

nav_price.png

634 ms

nav_compagin.png

nav_compagin.png

636 ms

nav_qupon.png

nav_qupon.png

635 ms

nav_store.png

nav_store.png

814 ms

nav_customers.png

nav_customers.png

814 ms

nav_contact.png

nav_contact.png

844 ms

menu_close.png

menu_close.png

843 ms

menu_open.png

menu_open.png

1256 ms

aside_title.png

aside_title.png

1014 ms

carrier_border.png

carrier_border.png

1015 ms

docomo_aside.png

docomo_aside.png

1051 ms

carrier_a_back.png

carrier_a_back.png

1051 ms

au_aside.png

au_aside.png

1081 ms

ymobile_aside.png

ymobile_aside.png

1215 ms

uqm_aside.png

uqm_aside.png

1216 ms

uq_aside.png

uq_aside.png

1260 ms

siro_aside.png

siro_aside.png

1260 ms

dot_sankaku.png

dot_sankaku.png

1296 ms

aside_staff.png

aside_staff.png

1418 ms

aside_reqruit.png

aside_reqruit.png

1419 ms

aside_nail.png

aside_nail.png

1481 ms

aside_hanko.jpg

aside_hanko.jpg

1481 ms

aside_id.png

aside_id.png

1441 ms

JZvgOA5uue.png

JZvgOA5uue.png

78 ms

mv_iphone15.jpg

mv_iphone15.jpg

1509 ms

mv01.jpg

mv01.jpg

1419 ms

mv06.jpg

mv06.jpg

1807 ms

c_docomo_pc.png

c_docomo_pc.png

1469 ms

d01.png

d01.png

1470 ms

d02.png

d02.png

1277 ms

d03.png

d03.png

1414 ms

d00.png

d00.png

1469 ms

btn_price_sp.png

btn_price_sp.png

1472 ms

c_au_pc.png

c_au_pc.png

1470 ms

addfriends_ja.png

addfriends_ja.png

664 ms

au01.png

au01.png

1311 ms

au02.png

au02.png

1414 ms

au03.png

au03.png

1469 ms

au00.png

au00.png

1468 ms

c_ymobile_pc.png

c_ymobile_pc.png

1469 ms

y01.png

y01.png

1317 ms

y02.png

y02.png

1407 ms

y00.png

y00.png

1381 ms

c_uqm_pc.png

c_uqm_pc.png

1468 ms

uqm01.png

uqm01.png

1437 ms

ga.js

ga.js

11 ms

sdk.js

sdk.js

51 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

139 ms

__utm.gif

__utm.gif

25 ms

sdk.js

sdk.js

5 ms

41 ms

uqm02.png

uqm02.png

1299 ms

uqm00.png

uqm00.png

1328 ms

c_uq_pc.png

c_uq_pc.png

1371 ms

uq99.png

uq99.png

1373 ms

settings

settings

95 ms

uq00.png

uq00.png

1442 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

21 ms

telecomland

telecomland

64 ms

bnr_price_pc.png

bnr_price_pc.png

1309 ms

bnr_shirorom_pc.png

bnr_shirorom_pc.png

1510 ms

bnr_qupon_pc.png

bnr_qupon_pc.png

1298 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

22 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

43 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

66 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

75 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

91 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

94 ms

_buildManifest.js

_buildManifest.js

104 ms

_ssgManifest.js

_ssgManifest.js

103 ms

bnr_plan.png

bnr_plan.png

1367 ms

bnr_nmp.png

bnr_nmp.png

1365 ms

bnr_downroad.png

bnr_downroad.png

1436 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

22 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

18 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

24 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

36 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

44 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

65 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

27 ms

rss_icon.gif

rss_icon.gif

1313 ms

tab_back.png

tab_back.png

1341 ms

tab_open.png

tab_open.png

1344 ms

tab_close.png

tab_close.png

1346 ms

phone_back.png

phone_back.png

1452 ms

red_back.png

red_back.png

1324 ms

funabashi.jpg

funabashi.jpg

1265 ms

kanamachi.jpg

kanamachi.jpg

1292 ms

bnr_store_sp.png

bnr_store_sp.png

1348 ms

fb_bk.png

fb_bk.png

1319 ms

footer_back.png

footer_back.png

1327 ms

bx_loader.gif

bx_loader.gif

1263 ms

controls.png

controls.png

1263 ms

Accessibility Review

telecom-land.jp accessibility score

63

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

telecom-land.jp best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

telecom-land.jp SEO score

81

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Telecom-land.jp 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 Telecom-land.jp main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

telecom-land.jp

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