Tools & Wizards About Us
iphone13.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

iphone13.com

iPhone13 予約・在庫ログ

Page Load Speed

5.7 sec in total

First Response

425 ms

Resources Loaded

4.5 sec

Page Rendered

726 ms

iphone13.com screenshot

About Website

Visit iphone13.com now to see the best up-to-date IPhone13 content for Japan and also check out these interesting facts you probably never knew about iphone13.com

2021年はiPhone13 Proを予約します！2007年の初代iPhoneから、毎年新型iPhoneを予約してしまうiPhoneコレクターの記録

Visit iphone13.com

Key Findings

We analyzed Iphone13.com page load time and found that the first response time was 425 ms and then it took 5.2 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

iphone13.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.2

62/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

iphone13.com

425 ms

www.iphone13.com

982 ms

styles.css

763 ms

mt.js

772 ms

jquery.min.js

30 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 39% of them (25 requests) were addressed to the original Iphone13.com, 11% (7 requests) were made to Ad.jp.ap.valuecommerce.com and 11% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Iphone13.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 168.2 kB (34%)

Content Size

500.3 kB

After Optimization

332.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iphone13.com main page is 500.3 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. 45% of websites need less resources to load. Images take 298.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 46.6 kB

  • Original 59.2 kB
  • After minification 57.3 kB
  • After compression 12.7 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 46.6 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 17.2 kB

  • Original 298.5 kB
  • After minification 281.3 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. IPhone13 images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 78.6 kB

  • Original 110.5 kB
  • After minification 91.3 kB
  • After compression 31.9 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 78.6 kB or 71% of the original size.

CSS Optimization

-81%

Potential reduce by 25.8 kB

  • Original 32.0 kB
  • After minification 25.5 kB
  • After compression 6.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. Iphone13.com needs all CSS files to be minified and compressed as it can save up to 25.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (41%)

Requests Now

61

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iphone13.com

iphone13.com

425 ms

www.iphone13.com

www.iphone13.com

982 ms

styles.css

styles.css

763 ms

mt.js

mt.js

772 ms

jquery.min.js

jquery.min.js

30 ms

myscript.js

myscript.js

310 ms

pagetop.js

pagetop.js

392 ms

plusone.js

plusone.js

49 ms

bookmark_button.js

bookmark_button.js

343 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

181 ms

button-only@2x.png

button-only@2x.png

181 ms

header.jpg

header.jpg

1184 ms

yoyakukeijibanbna.png

yoyakukeijibanbna.png

856 ms

iphone-se-kakaku474A2906-thumb-300xauto-184.jpg

iphone-se-kakaku474A2906-thumb-300xauto-184.jpg

628 ms

iphonese-321474A2869-thumb-300xauto-183.jpg

iphonese-321474A2869-thumb-300xauto-183.jpg

719 ms

iphone-se-new4inchmodel-thumb-300xauto-182.jpg

iphone-se-new4inchmodel-thumb-300xauto-182.jpg

734 ms

iphone5se-zumen110-thumb-300xauto-176.jpg

iphone5se-zumen110-thumb-300xauto-176.jpg

958 ms

ymobile-iphone5s474A2944-thumb-300xauto-166.jpg

ymobile-iphone5s474A2944-thumb-300xauto-166.jpg

1413 ms

iphone5seyoyakutassaku474A2860-thumb-300xauto-162.jpg

iphone5seyoyakutassaku474A2860-thumb-300xauto-162.jpg

1339 ms

iphone5se-pinkss-thumb-300xauto-160.jpg

iphone5se-pinkss-thumb-300xauto-160.jpg

1225 ms

iphone5se69mm-thumb-300xauto-159.jpg

iphone5se69mm-thumb-300xauto-159.jpg

1632 ms

iphone5se-kakaku474A2637-thumb-300xauto-157.jpg

iphone5se-kakaku474A2637-thumb-300xauto-157.jpg

1439 ms

iphone5se-hatubaibi02-thumb-300xauto-154.jpg

iphone5se-hatubaibi02-thumb-300xauto-154.jpg

1789 ms

iphon6s-7gazou.jpg

iphon6s-7gazou.jpg

1581 ms

5seget.jpg

5seget.jpg

1894 ms

6staiken128.jpg

6staiken128.jpg

2000 ms

iphone6sstock120.jpg

iphone6sstock120.jpg

2027 ms

top.png

top.png

1884 ms

all.js

all.js

130 ms

widgets.js

widgets.js

19 ms

coolicon.woff

coolicon.woff

2575 ms

htmlbanner

htmlbanner

336 ms

htmlbanner

htmlbanner

344 ms

arrow_02.png

arrow_02.png

2132 ms

tag.js

tag.js

34 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

102 ms

fastbutton

fastbutton

137 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

92 ms

413 ms

tag

tag

80 ms

105 ms

xd_arbiter.php

xd_arbiter.php

98 ms

xd_arbiter.php

xd_arbiter.php

141 ms

postmessageRelay

postmessageRelay

68 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

22 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

38 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

34 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

113 ms

api.js

api.js

32 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

60 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

70 ms

1x1.gif

1x1.gif

312 ms

1x1.gif

1x1.gif

311 ms

1x1.gif

1x1.gif

332 ms

b7.jpeg

b7.jpeg

649 ms

jot

jot

169 ms

13.jpeg

13.jpeg

321 ms

reset.css

reset.css

11 ms

entry-button.css

entry-button.css

11 ms

bbtn-s_v3.png

bbtn-s_v3.png

4 ms

ya.js

ya.js

316 ms

like.php

like.php

67 ms

-1cfYrhulAt.js

-1cfYrhulAt.js

134 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

142 ms

Accessibility Review

iphone13.com accessibility score

69

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

iphone13.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

iphone13.com SEO score

91

Search Engine Optimization Advices

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 Iphone13.com 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 Iphone13.com 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

iphone13.com

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