13.9 sec in total
709 ms
12.3 sec
940 ms
Welcome to eiyaaa.com homepage info - get ready to check Eiyaaa best content for Japan right away, or after learning these important things about eiyaaa.com
エイヤーは、白ロム・中古携帯の買取販売サイトです。NTTドコモ(FOMA)・au(KDDI)・ソフトバンク(SoftBank)・ウィルコム(WILLCOM)など各キャリアの白ロム・中古携帯・スマートフォンが豊富!
Visit eiyaaa.comWe analyzed Eiyaaa.com page load time and found that the first response time was 709 ms and then it took 13.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
eiyaaa.com performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value8.8 s
1/100
25%
Value10.7 s
7/100
10%
Value690 ms
43/100
30%
Value0.245
51/100
15%
Value9.2 s
32/100
10%
709 ms
313 ms
314 ms
335 ms
508 ms
Our browser made a total of 185 requests to load all elements on the main page. We found that 60% of them (111 requests) were addressed to the original Eiyaaa.com, 9% (17 requests) were made to Gigaplus.makeshop.jp and 8% (15 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (7.5 sec) belongs to the original domain Eiyaaa.com.
Page size can be reduced by 414.5 kB (11%)
3.8 MB
3.4 MB
In fact, the total size of Eiyaaa.com main page is 3.8 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. 60% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 110.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. This page needs HTML code to be minified as it can gain 27.4 kB, which is 22% 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 110.3 kB or 87% of the original size.
Potential reduce by 177.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. Eiyaaa images are well optimized though.
Potential reduce by 80.2 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 80.2 kB or 57% of the original size.
Potential reduce by 46.7 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. Eiyaaa.com needs all CSS files to be minified and compressed as it can save up to 46.7 kB or 82% of the original size.
Number of requests can be reduced by 67 (37%)
182
115
The browser has sent 182 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eiyaaa. 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 from 14 to 1 for CSS and as a result speed up the page load time.
eiyaaa.com
709 ms
m_sys_common.css
313 ms
import.css
314 ms
script.js
335 ms
jquery.min.js
508 ms
jquery.bxslider.min.js
339 ms
jquery.bxslider.css
464 ms
check_history.css
310 ms
pager.css
338 ms
shopdetail.css
364 ms
ranking.css
341 ms
basket.css
492 ms
security.css
527 ms
category_menu.css
645 ms
topicpath.css
669 ms
catalog.css
674 ms
ga.js
29 ms
sale.jpg
517 ms
count2.makeshop.jp
535 ms
logo.gif
157 ms
hNav02.png
158 ms
hNav03.png
319 ms
searchTitle.png
318 ms
l_searchBtn.png
337 ms
l_memberBtn.png
339 ms
l_mailBtn.png
491 ms
line.jpg
688 ms
bannertitle.gif
629 ms
eiyaaa_touch.jpg
630 ms
eiyaaa_kaitori.jpg
649 ms
eiyaaa_honten.jpg
675 ms
eiyaaa_kaigaisim.jpg
821 ms
eiyaaa_vpn.jpg
941 ms
left_edge.gif
988 ms
right_edge.gif
1008 ms
main_logo.jpg
1305 ms
newstitle.gif
1041 ms
maintitle2.gif
1134 ms
0000000045193.jpg
1298 ms
0000000053413.jpg
1306 ms
0000000053383.jpg
1326 ms
0000000049593.jpg
1388 ms
0000000053393.jpg
1624 ms
0000000043013.jpg
1637 ms
0000000053403.jpg
1639 ms
0000000053263.jpg
1666 ms
0000000053373.jpg
1706 ms
0000000053293.jpg
1960 ms
0000000053333.jpg
1975 ms
0000000053183.jpg
1992 ms
0000000053193.jpg
2812 ms
0000000046623.jpg
2302 ms
0000000053153.jpg
2309 ms
0000000053123.jpg
2329 ms
riyouseigen.jpg
551 ms
kyaria.jpg
552 ms
docomo.jpg
559 ms
au.jpg
579 ms
softbank.jpg
588 ms
ymobile.jpg
661 ms
etc_t.jpg
731 ms
siri.jpg
728 ms
iphone.jpg
738 ms
galaxy.jpg
770 ms
xperia.jpg
795 ms
item.jpg
851 ms
sim.jpg
904 ms
sd.jpg
907 ms
etc.jpg
919 ms
hosyo.jpg
961 ms
0000000053063.jpg
2443 ms
__utm.gif
34 ms
aq_tag_aos.js
148 ms
491 ms
sdk.js
268 ms
maintitle_mobile.gif
2466 ms
000000005065.jpg
4181 ms
EM34BYVZ46DUGEQNJE6A
124 ms
000000005066.jpg
3180 ms
000000002729.jpg
3503 ms
000000002725.jpg
3300 ms
ranking_title.gif
2728 ms
179 ms
xd_arbiter.php
208 ms
xd_arbiter.php
336 ms
0000000046612.jpg
3102 ms
gmsync
305 ms
segmentation.js
24 ms
302 ms
cnt
318 ms
0000000007782.jpg
3447 ms
0000000039772.jpg
3649 ms
0000000050072.jpg
4115 ms
0000000040672.jpg
3899 ms
xper_01.jpg
3801 ms
000000000778.jpg
4438 ms
000000004684.jpg
4514 ms
000000003047.jpg
4588 ms
000000005205.jpg
4645 ms
xper_02.jpg
4221 ms
gla_01.jpg
4261 ms
000000004106.jpg
5310 ms
000000004111.jpg
5400 ms
000000004755.jpg
5520 ms
000000005264.jpg
7477 ms
gla_02.jpg
4907 ms
maintitle1.gif
4390 ms
0000000052113.jpg
4707 ms
0000000051983.jpg
4987 ms
0000000051803.jpg
5010 ms
0000000051283.jpg
5215 ms
0000000047623.jpg
5013 ms
0000000051383.jpg
5057 ms
0000000051813.jpg
5043 ms
0000000047863.jpg
4859 ms
0000000050633.jpg
4942 ms
0000000050733.jpg
4954 ms
0000000050443.jpg
4904 ms
0000000051453.jpg
4753 ms
0000000051423.jpg
4668 ms
0000000051413.jpg
4523 ms
0000000050643.jpg
4132 ms
maintitle_mvno.gif
4093 ms
000000002730.jpg
4450 ms
000000002731.jpg
4286 ms
000000002735.jpg
4176 ms
000000002736.jpg
3851 ms
pagetopBtn.png
3661 ms
body_bg.png
3844 ms
hNav01.png
3847 ms
headBasketSwitch1.png
3657 ms
gNav01.png
3188 ms
gNav02.png
3324 ms
gNav03.png
3266 ms
gNav04.png
3299 ms
gNav05.png
3179 ms
rankIcon1.png
3128 ms
rankIcon2.png
2885 ms
rankIcon3.png
2696 ms
rankIcon4.png
2727 ms
rankIcon5.png
2495 ms
footerDot.png
2490 ms
beacon.html
10 ms
pixel
12 ms
cs
537 ms
Pug
17 ms
set
302 ms
sd
3 ms
tap.php
5 ms
pixel
13 ms
sync
4 ms
sync
312 ms
page.php
262 ms
ymuLUiC-7lH.css
275 ms
RrjF9eXlpRH.css
342 ms
mm0vjjrXdxr.js
541 ms
k0CDXajo9Lr.js
476 ms
ejW2OdYb_ED.js
609 ms
xnHNQrGmQZq.js
621 ms
8uSXvkyKRnL.js
621 ms
3rXe1-E34lR.js
621 ms
mapuser
149 ms
sync
158 ms
sync
163 ms
10945629_1548383868743019_3201914399332654974_n.jpg
287 ms
10359147_322455684573478_111967799863632242_n.jpg
346 ms
600708_115008535306557_835494321_n.jpg
414 ms
1977014_308168692710505_2586838662561365928_n.jpg
480 ms
12669710_924519577663039_8546787274176962304_n.jpg
481 ms
12573172_799848163494465_9166757571190534003_n.jpg
483 ms
10580032_582389761908706_8371261223001113686_n.jpg
482 ms
12079080_737531989724250_8254899028069934276_n.jpg
482 ms
11255736_103731976628333_3486431143760375062_n.jpg
482 ms
12345629_794225687366760_8167351076929991801_n.jpg
546 ms
11204412_1469603173353377_7762351294181318789_n.jpg
548 ms
21141_370374313083297_1969748891_n.jpg
548 ms
12541151_610770935729099_412358588425191554_n.jpg
575 ms
12565551_777181985720806_1353917773678820243_n.jpg
547 ms
wL6VQj7Ab77.png
110 ms
s7jcwEQH7Sx.png
109 ms
NWHVBMQg_9r.png
68 ms
R9a_DtVRZgv.js
69 ms
cUDgRFxaoIk.js
69 ms
hwOj1ZVxgid.js
70 ms
kDOzhTr2W91.js
70 ms
eiyaaa.com 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
eiyaaa.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
eiyaaa.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eiyaaa.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Eiyaaa.com 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.
eiyaaa.com
Open Graph description is not detected on the main page of Eiyaaa. 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: