15.6 sec in total
788 ms
14.5 sec
350 ms
Welcome to appletoner.jp homepage info - get ready to check Appletoner best content for Japan right away, or after learning these important things about appletoner.jp
ここでしか取得できない、優良文字列ドメイン名、著名サイトドメイン名等希少ドメイン名多数アリ!誰でもカンタン参加可能
Visit appletoner.jpWe analyzed Appletoner.jp page load time and found that the first response time was 788 ms and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
appletoner.jp performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value3.9 s
53/100
25%
Value4.8 s
67/100
10%
Value50 ms
100/100
30%
Value0.26
47/100
15%
Value3.5 s
92/100
10%
788 ms
187 ms
361 ms
548 ms
537 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 45% of them (54 requests) were addressed to the original Appletoner.jp, 53% (64 requests) were made to Gigaplus.makeshop.jp and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (11.6 sec) relates to the external source Gigaplus.makeshop.jp.
Page size can be reduced by 195.7 kB (14%)
1.4 MB
1.2 MB
In fact, the total size of Appletoner.jp 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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 53.8 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 53.8 kB or 85% of the original size.
Potential reduce by 123.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. Appletoner images are well optimized though.
Potential reduce by 474 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 17.6 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. Appletoner.jp needs all CSS files to be minified and compressed as it can save up to 17.6 kB or 64% of the original size.
Number of requests can be reduced by 26 (22%)
118
92
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Appletoner. 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 CSS and as a result speed up the page load time.
appletoner.jp
788 ms
m_sys_common.css
187 ms
import.css
361 ms
jquery.min.js
548 ms
applecat.css
537 ms
style.css
45 ms
jquery.min.js
22 ms
slide.css
580 ms
slides.min.jquery.js
682 ms
check_history.css
345 ms
pager.css
321 ms
shopdetail.css
361 ms
ranking.css
366 ms
basket.css
418 ms
security.css
495 ms
category_menu.css
504 ms
topicpath.css
518 ms
catalog.css
536 ms
ordercontract.css
545 ms
toplogo-3.2.jpg
96 ms
appletoner_01.png
94 ms
appletoner_02.png
384 ms
appletoner_03.png
401 ms
appletoner_04.png
402 ms
ink_title-2.jpg
95 ms
toner_title-2.jpg
121 ms
bg_bar.jpg
611 ms
receipt.jpg
120 ms
kisyaTop.jpg
124 ms
001.jpg
2171 ms
002.jpg
125 ms
003.gif
95 ms
pctop2_01.jpg
123 ms
pctop2_03.gif
123 ms
pctop2_11.jpg
124 ms
apple-bar-2.jpg
889 ms
ink-140128.jpg
1477 ms
apple-bar-1.jpg
1028 ms
crg-418-131129-2.jpg
1049 ms
crg322ii.jpg
123 ms
crg-502-131129-2.jpg
1270 ms
ep86.jpg
140 ms
crg303.jpg
145 ms
crg304.jpg
147 ms
crg312.jpg
140 ms
crg508.jpg
140 ms
npg35.jpg
145 ms
epj.jpg
141 ms
ep22.jpg
146 ms
tn195.jpg
143 ms
tn290.jpg
147 ms
tn395.jpg
160 ms
tn04.jpg
164 ms
tn26j.jpg
159 ms
tn37j.jpg
833 ms
menu_01.gif
266 ms
menu_02.gif
266 ms
menu_03.gif
264 ms
menu_04.gif
265 ms
menu_05.gif
261 ms
menu_06.gif
262 ms
menu_07.gif
446 ms
searchbox03.jpg
468 ms
searchbox06.gif
523 ms
004.png
673 ms
bottom.gif
455 ms
is_show_gmo_header.html
583 ms
tn-48j-131129.jpg
1470 ms
tn-6600-131129.jpg
1607 ms
lpc4t8.jpg
64 ms
lpca4etc5.jpg
38 ms
lpca3etc2-1.jpg
1642 ms
lpca3etc9.jpg
76 ms
lpb4t15.jpg
60 ms
lpa3etc10.jpg
58 ms
lpa4etc7.jpg
58 ms
lpa4kut4.jpg
755 ms
nec_bar_131129.jpg
1839 ms
pr-l5600c-131129.jpg
2199 ms
pr-l5700c-131129.jpg
2400 ms
pr-l2900c-131129.jpg
2351 ms
pr-l7500c-131129.jpg
2440 ms
oki_bar_131129.jpg
2468 ms
c301dn-131129.jpg
2788 ms
c3400n-131129.jpg
2970 ms
c5800dn-131129.jpg
3125 ms
c810dn-131129.jpg
3204 ms
ricoh_bar_131129.jpg
3202 ms
c220-131129.jpg
3074 ms
c710-131129.jpg
3424 ms
c820h-131129.jpg
3753 ms
400b-131129.jpg
11627 ms
body_02.gif
209 ms
ico-arr.gif
199 ms
btn.gif
213 ms
pay_01.jpg
452 ms
flyoki.jpg
310 ms
flycanon.jpg
347 ms
flyepson.jpg
351 ms
flybrother.jpg
382 ms
flynec.jpg
487 ms
flyxerox.jpg
527 ms
flyricoh.jpg
358 ms
flylexmark.jpg
398 ms
flydell.jpg
403 ms
flyhp.jpg
442 ms
flyibm.jpg
538 ms
flycasio.jpg
560 ms
rankmono.jpg
397 ms
rankingcanon02.jpg
414 ms
rankingcanon04.jpg
422 ms
rankcolor.jpg
474 ms
rankingcanon01.jpg
585 ms
rankfax.jpg
586 ms
rankingbrother02.jpg
431 ms
rankingbrother01.jpg
478 ms
rankingbrother04.jpg
464 ms
rankingepson04.jpg
506 ms
rankingepson01.jpg
646 ms
rankingepson02.jpg
605 ms
searchbo.gif
467 ms
appletoner.jp accessibility score
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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
appletoner.jp 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
appletoner.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
![]()
JA
![]()
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Appletoner.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 Appletoner.jp main page’s claimed encoding is euc-jp. 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.
appletoner.jp
Open Graph description is not detected on the main page of Appletoner. 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: