6.3 sec in total
1 sec
4.9 sec
432 ms
Click here to check amazing Aim E content. Otherwise, check out these important facts you probably never knew about aim-e.com
エイムグループは、外食店舗をプロデュースする会社です。
Visit aim-e.comWe analyzed Aim-e.com page load time and found that the first response time was 1 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
aim-e.com performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value5.7 s
17/100
25%
Value14.2 s
1/100
10%
Value340 ms
75/100
30%
Value0.97
2/100
15%
Value5.4 s
71/100
10%
1038 ms
506 ms
511 ms
526 ms
527 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Aim-e.com, 19% (26 requests) were made to Scontent.xx.fbcdn.net and 18% (24 requests) were made to Favo.smart-element.net. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Favo.smart-element.net.
Page size can be reduced by 909.9 kB (37%)
2.4 MB
1.5 MB
In fact, the total size of Aim-e.com main page is 2.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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 51.4 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 16.3 kB, which is 27% 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 51.4 kB or 84% of the original size.
Potential reduce by 141.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. Obviously, Aim E needs image optimization as it can save up to 141.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 502.0 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 502.0 kB or 64% of the original size.
Potential reduce by 214.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. Aim-e.com needs all CSS files to be minified and compressed as it can save up to 214.6 kB or 83% of the original size.
Number of requests can be reduced by 60 (47%)
127
67
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aim E. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
aim-e.com
1038 ms
common.css
506 ms
reset.css
511 ms
default.css
526 ms
default.css
527 ms
tipTip.css
527 ms
js
26 ms
jquery.min.js
35 ms
jquery.easing.1.3.js
557 ms
imagesLoaded.js
822 ms
jquery.tipTip.js
836 ms
default.js
870 ms
common.js
877 ms
top.css
880 ms
shopInfo.css
871 ms
top.js
1154 ms
jquery.cycle.all.js
22 ms
jquery.cycle.all.js
21 ms
1405221902.png
632 ms
analytics.js
13 ms
collect
16 ms
1372470053-resize-160x0.png
673 ms
1405071853-fit-1000x380.jpg
1491 ms
1405071868-fit-1000x380.jpg
1677 ms
1405071881-fit-1000x380.jpg
1785 ms
1405076094-fit-1000x380.jpg
1793 ms
1405071900-fit-1000x380.jpg
1791 ms
1405067629-resize-220x220.jpg
894 ms
1405067849-resize-220x220.jpg
1700 ms
1405067839-resize-220x220.jpg
1993 ms
1406522665-fit-170x69.gif
2011 ms
1405397827-fit-170x69.gif
2031 ms
1372404210-fit-170x69.gif
2124 ms
1372404678-fit-170x69.jpg
2135 ms
1405398144-fit-170x69.png
2306 ms
1372404358-fit-170x69.jpg
2353 ms
1372404419-fit-170x69.jpg
2355 ms
1372404497-fit-170x69.gif
2407 ms
1372404559-fit-170x69.gif
2486 ms
1372404318-fit-170x69.jpg
2485 ms
1416634198-fit-170x69.gif
2625 ms
1416634167-fit-170x69.gif
2671 ms
1437719048-fit-170x69.gif
2705 ms
1405398171-fit-170x69.png
2924 ms
1447734359-fit-170x69.png
2836 ms
1447927244-fit-170x69.png
2837 ms
fb02.png
209 ms
twitter.png
393 ms
mixi.png
392 ms
google.png
397 ms
news3.png
633 ms
sdk.js
351 ms
common.js
41 ms
map.js
69 ms
util.js
72 ms
marker.js
70 ms
aim-e.com
669 ms
crdgFIoyMQo
135 ms
StaticMapService.GetMapImage
137 ms
likebox.php
402 ms
onion.js
52 ms
openhand_8_8.cur
42 ms
www-embed-player-vflfNyN_r.css
68 ms
www-embed-player.js
93 ms
ViewportInfoService.GetViewportInfo
51 ms
stats.js
44 ms
controls.js
105 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
200 ms
ad_status.js
196 ms
spotlight-poi.png
62 ms
css
165 ms
transparent.png
137 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
151 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
185 ms
vt
97 ms
vt
93 ms
vt
95 ms
vt
94 ms
vt
160 ms
google4.png
90 ms
mapcnt6.png
90 ms
sv5.png
90 ms
143 ms
410ucuAGgaJ.css
347 ms
tSbl8xBI27R.css
415 ms
Czh0gDTFcBt.css
489 ms
Ek6lpayKeeB.css
619 ms
1kPfZUdGrka.js
691 ms
Yuj_Y8xNH2C.js
713 ms
Mpe38fuBVZ2.js
559 ms
n8qIhCw3vMx.js
558 ms
QKy94bWvcbp.js
556 ms
6q5od22S-uf.js
637 ms
7B-2ZS3Qt8r.js
744 ms
qcMicXoOToy.js
829 ms
57RpJa05x58.js
750 ms
xd_arbiter.php
259 ms
xd_arbiter.php
465 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
66 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
66 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
67 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
67 ms
AuthenticationService.Authenticate
199 ms
539889_125428234297082_318303018_n.jpg
378 ms
11215851_687443148056731_7189729131553901352_n.jpg
434 ms
5223_1676855715903609_2352002736280388922_n.jpg
502 ms
12279046_886888788068057_9075526684280099609_n.jpg
565 ms
10273875_956398607778987_5277953772012680440_n.jpg
568 ms
12106804_537690586382019_4737650412623970071_n.jpg
749 ms
12439392_536851426488092_3939218821986242660_n.jpg
628 ms
12670406_536851486488086_2458221468338036977_n.jpg
607 ms
12805770_536851546488080_696493169919853029_n.jpg
700 ms
943964_536851963154705_5522814679691852899_n.jpg
718 ms
12278802_500340046805897_5252692932165868429_n.jpg
1016 ms
12246995_500340073472561_4011181147135034674_n.jpg
715 ms
12219541_500340166805885_3862417511397887567_n.jpg
735 ms
12246819_500340126805889_2314164551719052923_n.jpg
811 ms
11218710_460575637449005_5655866517820069231_n.jpg
811 ms
11737961_460575994115636_8013133009557689903_n.jpg
845 ms
11262370_460576064115629_7252642150986968039_n.jpg
863 ms
11011212_460576137448955_2142260574162331238_n.jpg
994 ms
11061226_419330558240180_228491810301551965_n.jpg
1014 ms
603783_419330524906850_8212261456955400489_n.jpg
937 ms
11133812_419330508240185_1083752973964989157_n.jpg
985 ms
11084252_419330531573516_6208678099156010731_n.jpg
1015 ms
10846005_369939243179312_3821144673336705897_n.png
1077 ms
1907887_369939349845968_4283273660988681078_n.jpg
1078 ms
1470323_369939409845962_4935567737787258702_n.jpg
1119 ms
10394093_369939463179290_912282176279242267_n.jpg
1285 ms
wL6VQj7Ab77.png
94 ms
s7jcwEQH7Sx.png
96 ms
QDwYpIaRyfG.png
96 ms
K00K-UgnsKu.png
95 ms
VXcANLwwL5J.js
69 ms
AmlxWlqMvlv.js
135 ms
aim-e.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
aim-e.com 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
aim-e.com 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aim-e.com 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 Aim-e.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.
aim-e.com
Open Graph description is not detected on the main page of Aim E. 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: