8.2 sec in total
530 ms
7.4 sec
191 ms
Click here to check amazing Atinn content for Japan. Otherwise, check out these important facts you probably never knew about atinn.jp
アットインは東京、横浜、名古屋、大阪など主要都市を中心にマンスリーマンションを展開。出張や転勤、一時的な仮住まい、受験など様々な用途でご利用いただけます。
Visit atinn.jpWe analyzed Atinn.jp page load time and found that the first response time was 530 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
atinn.jp performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.6 s
34/100
25%
Value6.8 s
34/100
10%
Value410 ms
66/100
30%
Value0
100/100
15%
Value9.2 s
32/100
10%
530 ms
308 ms
316 ms
323 ms
328 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 86% of them (80 requests) were addressed to the original Atinn.jp, 3% (3 requests) were made to Googleadservices.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Atinn.jp.
Page size can be reduced by 546.7 kB (25%)
2.2 MB
1.6 MB
In fact, the total size of Atinn.jp main page is 2.2 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. 40% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 38.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. 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 38.4 kB or 79% of the original size.
Potential reduce by 7.7 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. Atinn images are well optimized though.
Potential reduce by 398.1 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 398.1 kB or 66% of the original size.
Potential reduce by 102.5 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. Atinn.jp needs all CSS files to be minified and compressed as it can save up to 102.5 kB or 86% of the original size.
Number of requests can be reduced by 36 (41%)
88
52
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Atinn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
atinn.jp
530 ms
sgt_reset.css
308 ms
new_generic.css
316 ms
generic2.css
323 ms
bland.css
328 ms
lines.css
329 ms
jquery-ui-1.8.16.custom.css
365 ms
ddsmoothmenu.css
646 ms
jquery-1.6.2.min.js
1027 ms
jquery.gafunc.min.js
672 ms
jquery-ui-1.8.16.custom.min.js
1241 ms
jquery.ui.datepicker-ja.js
700 ms
jquery.page-scroller-308.js
687 ms
generic.js
964 ms
ddsmoothmenu.js
996 ms
navigator.js
1049 ms
init.js
1060 ms
shiny.js
1285 ms
slidermenu.js
1318 ms
jquery.id.chopslider-2.0.5.free.min.js
1347 ms
jquery.id.cstransitions-1.0.min.js
1376 ms
top.clickable.min.js
1386 ms
jquery.chopslider.css
1565 ms
conversion.js
20 ms
ga.js
32 ms
tag.js
9 ms
tag
16 ms
__utm.gif
13 ms
f67e24269d78c6808cc0f43476bf910304719c70.js
37 ms
BrightTag.jquery-1.5.1.js
4 ms
header_bg.png
345 ms
header_logo.png
346 ms
efct_shiny.png
362 ms
header-badge.png
382 ms
contact.png
392 ms
header_menu_bg.png
567 ms
head01.png
627 ms
head02.png
671 ms
head03.png
703 ms
head04.png
700 ms
head05.png
697 ms
head08.png
895 ms
head07.png
949 ms
newsbtn_back.png
992 ms
670_6776523620150421064032.jpg
1470 ms
670_6382901520140827105647.jpg
1674 ms
670_8083879520150928060801.jpg
1810 ms
670_2594906020140623102342.jpg
1804 ms
670_3509188220140421045613.jpg
1901 ms
670_4024917720140729040954.jpg
2278 ms
670_1775347220140421051659.jpg
2757 ms
670_5226905620140421051127.jpg
2802 ms
670_7971544420140501112104.jpg
2574 ms
670_0695054420140421052405.jpg
2699 ms
670_1718409820131030032112.jpg
3209 ms
670_5689143620120521022559.jpg
3344 ms
670_6962000420151221113330.jpg
3702 ms
670_5710031620151221113408.jpg
3611 ms
670_9918144520150311120056.jpg
3738 ms
300_6645513320140515103325.gif
3283 ms
5points.png
3692 ms
4812228920150421064026.jpg
4064 ms
5691154520140827105642.jpg
3973 ms
8845050920150928054959.jpg
4282 ms
4823556520140623100949.jpg
4134 ms
88 ms
conversion_async.js
96 ms
prefs
3934 ms
3066741820140421044154.jpg
3894 ms
1193465020140731085814.jpg
4299 ms
37 ms
leftbanner_01.png
4049 ms
28 ms
leftbanner_02.png
4302 ms
leftbanner_03.png
4151 ms
65 ms
60 ms
leftbanner_06.png
4043 ms
leftbanner_04.png
4074 ms
leftbanner_05.png
4064 ms
leftbanner_08.png
4168 ms
120_8981783120160107053934.jpg
4228 ms
120_0311468720160229123037.jpg
4299 ms
120_1873331520160216030614.jpg
4129 ms
link-gotop.gif
4095 ms
rireki_innner.png
4102 ms
train.gif
3752 ms
user.png
3678 ms
money_yen.png
3551 ms
footer_bg.png
3533 ms
footer_logo.png
3470 ms
right.gif
3135 ms
spacer.gif
3007 ms
atinn.jp accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
atinn.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
atinn.jp 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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Atinn.jp 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 Atinn.jp 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.
atinn.jp
Open Graph description is not detected on the main page of Atinn. 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: