10.1 sec in total
2 sec
7.5 sec
599 ms
Visit sim-smartphone.net now to see the best up-to-date Sim Smartphone content for Japan and also check out these interesting facts you probably never knew about sim-smartphone.net
格安SIMとスマホライフ
Visit sim-smartphone.netWe analyzed Sim-smartphone.net page load time and found that the first response time was 2 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
sim-smartphone.net performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value6.1 s
12/100
25%
Value11.7 s
4/100
10%
Value5,300 ms
0/100
30%
Value0.003
100/100
15%
Value15.2 s
7/100
10%
1978 ms
846 ms
540 ms
364 ms
1298 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 72% of them (70 requests) were addressed to the original Sim-smartphone.net, 4% (4 requests) were made to Thumbnail.image.rakuten.co.jp and 4% (4 requests) were made to Static.affiliate.rakuten.co.jp. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Sim-smartphone.net.
Page size can be reduced by 590.1 kB (28%)
2.1 MB
1.6 MB
In fact, the total size of Sim-smartphone.net main page is 2.1 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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 85.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 85.7 kB or 82% of the original size.
Potential reduce by 127.8 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. Sim Smartphone images are well optimized though.
Potential reduce by 214.6 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 214.6 kB or 65% of the original size.
Potential reduce by 162.1 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. Sim-smartphone.net needs all CSS files to be minified and compressed as it can save up to 162.1 kB or 89% of the original size.
Number of requests can be reduced by 36 (38%)
96
60
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sim Smartphone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
sim-smartphone.net
1978 ms
style.css
846 ms
comment-style.css
540 ms
screen.min.css
364 ms
jquery.js
1298 ms
jquery-migrate.min.js
572 ms
modernizr.js
373 ms
jscript.js
548 ms
scroll.js
554 ms
comment.js
592 ms
fixed_ad.js
728 ms
japanese.css
735 ms
wp-emoji-release.min.js
574 ms
rakuten_widget.js
1006 ms
front.min.js
360 ms
bgt
920 ms
0.gif
335 ms
bgt
874 ms
bgt
874 ms
0.gif
374 ms
0.gif
354 ms
menu_background.gif
181 ms
shadow.png
184 ms
icon_home.png
171 ms
icon_search.png
182 ms
background2.gif
188 ms
logo.png
1051 ms
icon_rss.gif
340 ms
Blade-V6%E3%81%8C19800%E5%86%86%E3%81%AB%E5%80%A4%E4%B8%8B%E3%81%92%EF%BC%81ZenFone-Go%E3%81%A8%E3%81%AE%E6%AF%94%E8%BC%83-181x181.png
946 ms
icon_category.gif
362 ms
icon_tag.gif
365 ms
%E3%83%89%E3%82%B3%E3%83%A2%E3%81%8CGalaxy-S6-S6-edge%E3%81%ABAndroid-6.0%E3%81%AE%E3%82%A2%E3%83%83%E3%83%97%E3%83%87%E3%83%BC%E3%83%88%E6%8F%90%E4%BE%9B-181x181.png
972 ms
Nexus5X-Android-6.0.1%E3%81%8C%E3%82%B9%E3%83%AA%E3%83%BC%E3%83%97%E5%BE%A9%E5%B8%B0%E5%BE%8C%E3%80%81Wi-Fi%E3%81%AB%E7%B9%8B%E3%81%8C%E3%82%89%E3%81%AA%E3%81%84-181x181.png
1017 ms
Nexus5X%E3%81%AE%E6%B6%B2%E6%99%B6%E4%BF%9D%E8%AD%B7%E3%83%95%E3%82%A3%E3%83%AB%E3%83%A0-RT-NX5XFC1%E8%B3%BC%E5%85%A5%E3%83%AC%E3%83%93%E3%83%A5%E3%83%BC-181x181.png
1455 ms
Nexus5XLG-H791%E3%82%92%E8%B3%BC%E5%85%A5%E3%83%AC%E3%83%93%E3%83%A5%E3%83%BC%EF%BC%81%E6%8A%80%E9%81%A9%E7%A2%BA%E8%AA%8D%E3%82%84AXON-mini%E3%81%A8%E6%AF%94%E8%BC%83-181x181.png
1088 ms
ZenFone-GoZB551KL-%E6%A0%BC%E5%AE%89%E3%82%B9%E3%83%9E%E3%83%9B%E5%85%A5%E9%96%80%E6%A9%9F%EF%BC%81ZenFone-2-laser%E6%AF%94%E8%BC%83-181x181.png
1305 ms
%E6%A5%BD%E5%A4%A9%E3%81%A7%E3%82%93%E3%82%8F%E3%81%A8G-Call%E3%81%AE%E6%96%99%E9%87%91%E6%AF%94%E8%BC%83%EF%BC%81%E3%83%97%E3%83%AC%E3%83%95%E3%82%A3%E3%83%83%E3%82%AF%E3%82%B9%E7%95%AA%E5%8F%B7%E4%BB%98%E5%8A%A0%E3%81%A7%E7%AF%80%E7%B4%84-181x181.png
1341 ms
BLADE-V580%E3%82%92ZTE%E3%81%8C%E7%99%BA%E8%A1%A8%EF%BC%81GR5%E3%81%A8%E3%81%AE%E3%82%B9%E3%83%9A%E3%83%83%E3%82%AF%E6%AF%94%E8%BC%83-181x181.png
1355 ms
050%E3%82%A2%E3%83%97%E3%83%AA%E3%81%AE%E6%96%99%E9%87%91%E6%AF%94%E8%BC%83%EF%BC%81IP%E9%9B%BB%E8%A9%B1%E3%81%A7%E3%82%B9%E3%83%9E%E3%83%9B%E3%81%AE%E9%80%9A%E8%A9%B1%E6%96%99%E3%82%92%E7%AF%80%E7%B4%84-181x181.png
1813 ms
%E6%A0%BC%E5%AE%89SIM%E3%81%AE%E7%84%A1%E6%96%99%E9%80%9A%E8%A9%B1%E3%82%A2%E3%83%97%E3%83%AA%EF%BC%81%E5%AE%B6%E6%97%8F%E9%96%93%E9%80%9A%E8%A9%B1%E3%81%AE%E4%BB%A3%E6%9B%BF%E3%81%AB%E3%81%84%E3%81%8B%E3%81%8C%EF%BC%9F-181x181.png
1458 ms
%E6%A0%BC%E5%AE%89SIM%E3%81%AE%E5%AF%BE%E5%BF%9C%E3%83%90%E3%83%B3%E3%83%89%EF%BC%81%E5%AF%BE%E5%BF%9C%E5%91%A8%E6%B3%A2%E6%95%B0%E5%B8%AF%E3%81%AE%E7%A2%BA%E8%AA%8D-181x181.png
1844 ms
ZenFone-MaxZC550KL%E3%81%A8ZenFone-2-laser%E6%AF%94%E8%BC%83%EF%BC%811%E3%83%B5%E6%9C%88%E5%85%85%E9%9B%BB%E3%81%84%E3%82%89%E3%81%9A-181x181.png
1715 ms
%E6%A5%BD%E5%A4%A9%E3%83%A2%E3%83%90%E3%82%A4%E3%83%AB%E3%81%8C%E3%82%B3%E3%83%B3%E3%83%93%E3%83%8B%E5%8F%97%E3%81%91%E5%8F%96%E3%82%8A%E3%82%B5%E3%83%BC%E3%83%93%E3%82%B9%E3%82%92%E9%96%8B%E5%A7%8B%EF%BC%81%E5%8D%B3%E6%97%A5%E9%96%8B%E9%80%9A%E5%8F%AF%E8%83%BD-181x181.png
2032 ms
%E3%83%89%E3%82%B3%E3%83%A2%E3%81%8CXperia-Z5%E3%82%B7%E3%83%AA%E3%83%BC%E3%82%BA%E3%81%ABAndroid-6.0%E3%81%AE%E3%82%A2%E3%83%83%E3%83%97%E3%83%87%E3%83%BC%E3%83%88%E6%8F%90%E4%BE%9B-181x181.png
1794 ms
%E6%A0%BC%E5%AE%89SIM%E3%81%8C%E5%AE%89%E3%81%84%E7%90%86%E7%94%B1%EF%BC%81%E5%AE%89%E3%81%8B%E3%82%8D%E3%81%86%E6%82%AA%E3%81%8B%E3%82%8D%E3%81%86%E3%81%A7%E3%81%AF%E3%81%AA%E3%81%84-181x181.png
2215 ms
%E6%A5%BD%E5%A4%A9%E3%83%A2%E3%83%90%E3%82%A4%E3%83%AB%E3%80%802016.2%E6%9C%88-181x181.png
1901 ms
mineo-A%E3%83%97%E3%83%A9%E3%83%B3%E3%81%A8D%E3%83%97%E3%83%A9%E3%83%B3%E3%81%AE%E6%AF%94%E8%BC%83%EF%BC%81%E3%83%91%E3%82%B1%E3%83%83%E3%83%88%E3%82%B7%E3%82%A7%E3%82%A2%E7%AD%89%E3%81%8C%E9%9D%9E%E5%B8%B8%E3%81%AB%E8%B1%8A%E5%AF%8C-181x181.png
2333 ms
UQ-mobile-%E7%84%A1%E5%88%B6%E9%99%90%E3%83%97%E3%83%A9%E3%83%B3%E3%82%82%E3%81%82%E3%82%8A%EF%BC%81%E9%80%9F%E5%BA%A6%E3%81%AE%E8%A9%95%E5%88%A4%E3%81%A8%E5%8F%A3%E3%82%B3%E3%83%9F-181x181.png
2238 ms
Galaxy-S7%E3%81%A8Galaxy-S7-edge%E3%81%AE%E3%82%B9%E3%83%9A%E3%83%83%E3%82%AF%E6%AF%94%E8%BC%83%EF%BC%81%E7%99%BA%E5%A3%B2%E6%97%A5%E3%81%AF%E3%81%84%E3%81%A4%EF%BC%9F-181x181.png
2381 ms
Xperia-X-Performance%E3%81%AE%E3%81%BF%E3%81%8C%E6%97%A5%E6%9C%AC%E3%81%A7%E7%99%BA%E5%A3%B2%EF%BC%81%E3%82%B9%E3%83%9A%E3%83%83%E3%82%AF%E3%81%A8%E6%AF%94%E8%BC%83-181x181.png
2641 ms
%E4%B8%89%E5%A4%A7%E3%82%AD%E3%83%A3%E3%83%AA%E3%82%A2%E3%81%AE%E3%83%A1%E3%83%AA%E3%83%83%E3%83%88%EF%BC%81MVNO%E3%81%A8%E3%81%AE%E9%81%95%E3%81%84%E3%82%92%E6%AF%94%E8%BC%83-181x181.png
2707 ms
%E6%A0%BC%E5%AE%89SIM%E3%81%AE%E3%83%87%E3%83%A1%E3%83%AA%E3%83%83%E3%83%88%E3%82%84%E5%BC%B1%E7%82%B9%E3%81%AF%E3%81%AA%E3%81%84%E3%81%AE%E3%81%8B%EF%BC%9F-181x181.png
3121 ms
UQ-mobile%E3%80%80%E3%81%B4%E3%81%A3%E3%81%9F%E3%82%8A%E3%83%97%E3%83%A9%E3%83%B3%E3%81%8C%E9%AB%98%E3%81%84%EF%BC%81%E3%82%B9%E3%83%9E%E3%83%88%E3%82%AF%E5%89%B2%E3%81%A8%E3%83%9E%E3%83%B3%E3%82%B9%E3%83%AA%E3%83%BC%E5%89%B2-181x181.png
3384 ms
ONETOUCH-IDOL-3%E3%81%8C%E6%9C%9F%E9%96%93%E9%99%90%E5%AE%9A%E3%81%AE%E6%BF%80%E5%AE%89%E8%B2%A9%E5%A3%B2%EF%BC%81%E8%A9%95%E4%BE%A1%E3%81%A8%E3%83%AC%E3%83%93%E3%83%A5%E3%83%BC-181x181.png
3049 ms
%E3%82%A4%E3%82%AA%E3%83%B3%E3%83%A2%E3%83%90%E3%82%A4%E3%83%AB%E3%81%8CMVNO%E4%BA%8B%E6%A5%AD%E8%80%85%E3%81%AB%EF%BC%81%E6%96%99%E9%87%91%E4%BD%93%E7%B3%BB%E3%81%A8%E8%A9%95%E5%88%A4%E3%83%BB%E9%80%9F%E5%BA%A6-181x181.png
3279 ms
headline_background.gif
2742 ms
%E3%83%96%E3%83%AD%E3%82%B0%E7%AE%A1%E7%90%86%E4%BA%BA%E3%81%AE%E3%82%B9%E3%83%9E%E3%83%9B%E3%83%A9%E3%82%A4%E3%83%95.png
2953 ms
bullet1.gif
2849 ms
dot1.gif
3022 ms
SIM%E3%83%95%E3%83%AA%E3%83%BC4%E6%A9%9F%E7%A8%AE%E6%AF%94%E8%BC%83-181x181.jpg
3037 ms
Moto-G-%E7%AC%AC3%E4%B8%96%E4%BB%A3-181x181.png
3409 ms
honor6-Plus-Android5.1.1-%E3%82%A2%E3%83%83%E3%83%97%E3%83%87%E3%83%BC%E3%83%88-181x181.png
3844 ms
Huawei-p8lite-181x181.jpg
3051 ms
%E3%82%82%E3%81%97%E3%82%82%E3%82%B7%E3%83%BC%E3%82%AF%E3%82%B9-%E3%82%A2%E3%82%A4%E3%82%AD%E3%83%A3%E3%83%83%E3%83%81-181x181.jpg
3363 ms
SAMURAI-MIYABI-181x181.jpg
3459 ms
0046_200x200.jpg
969 ms
234x60.gif
786 ms
mtwidget04.affiliate.rakuten.co.jp
852 ms
all.js
271 ms
analytics.js
45 ms
collect
12 ms
124 ms
xd_arbiter.php
215 ms
xd_arbiter.php
422 ms
AXON-mini-181x181.png
3596 ms
NifMo%E3%81%A7%E3%82%93%E3%82%8F-%E3%82%A2%E3%82%A4%E3%82%AD%E3%83%A3%E3%83%83%E3%83%81-181x181.jpg
2603 ms
Nexus6P-181x181.jpg
2930 ms
au-181x181.png
2901 ms
honor6-Plus-181x181.jpg
3011 ms
honor6-Plus%E6%95%85%E9%9A%9C-181x181.jpg
2876 ms
%E3%83%89%E3%82%B3%E3%83%A2%E3%83%A1%E3%83%BC%E3%83%AB-%E3%82%A2%E3%82%A4%E3%82%AD%E3%83%A3%E3%83%83%E3%83%81-181x181.jpg
3162 ms
GR5-181x181.png
2955 ms
pc_pcview_all.css
11 ms
front_merged.js
31 ms
mtwidget03.affiliate.ashiato.rakuten.co.jp
644 ms
getMWConf.php
328 ms
loading.gif
28 ms
buttons.gif
11 ms
Arrows-M02-181x181.jpg
2938 ms
Nexus5X-181x181.jpg
2796 ms
return_top.png
2648 ms
imgrc0064631383.jpg
415 ms
a.gif
519 ms
no_image.gif
191 ms
imgrc0063239578.jpg
395 ms
nexus-4251.jpg
370 ms
mobile.css
540 ms
sim-smartphone.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
sim-smartphone.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
sim-smartphone.net SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sim-smartphone.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Sim-smartphone.net 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.
sim-smartphone.net
Open Graph description is not detected on the main page of Sim Smartphone. 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: