7.3 sec in total
426 ms
6 sec
899 ms
Welcome to a-t-g.jp homepage info - get ready to check A T G best content for Japan right away, or after learning these important things about a-t-g.jp
No botanical,No life.
Visit a-t-g.jpWe analyzed A-t-g.jp page load time and found that the first response time was 426 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
a-t-g.jp performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value15.2 s
0/100
25%
Value13.7 s
2/100
10%
Value3,460 ms
2/100
30%
Value0.001
100/100
15%
Value17.6 s
4/100
10%
426 ms
174 ms
347 ms
349 ms
362 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 63% of them (90 requests) were addressed to the original A-t-g.jp, 13% (19 requests) were made to Static.xx.fbcdn.net and 10% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain A-t-g.jp.
Page size can be reduced by 837.7 kB (11%)
7.5 MB
6.7 MB
In fact, the total size of A-t-g.jp main page is 7.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.8 MB which makes up the majority of the site volume.
Potential reduce by 43.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 43.4 kB or 78% of the original size.
Potential reduce by 231.5 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. A T G images are well optimized though.
Potential reduce by 334.4 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 334.4 kB or 73% of the original size.
Potential reduce by 228.4 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. A-t-g.jp needs all CSS files to be minified and compressed as it can save up to 228.4 kB or 85% of the original size.
Number of requests can be reduced by 65 (46%)
140
75
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A T G. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
a-t-g.jp
426 ms
wp-emoji-release.min.js
174 ms
style.css
347 ms
ParaAdmin.css
349 ms
color-picker.min.css
362 ms
style.css
379 ms
style.css
394 ms
base.css
400 ms
font-awesome.min.css
14 ms
styles.css
517 ms
gallery.css
520 ms
style.css
542 ms
style.css
566 ms
frontpage.css
589 ms
home.css
597 ms
style.css
686 ms
float.css
693 ms
list-cover.css
721 ms
lp.css
755 ms
style-since-20151203.css
783 ms
slider-pro.min.css
795 ms
archive-plants.css
855 ms
jquery.fancybox-1.3.7.min.css
866 ms
jquery.js
1084 ms
jquery-migrate.min.js
943 ms
related-post-scripts.js
979 ms
ParaAdmin.js
993 ms
jquery.galleriffic.js
1028 ms
float.js
1040 ms
list-cover.js
1130 ms
image-scale.js
1174 ms
jquery.easing.min.js
7 ms
jquery.sliderPro.min.js
1392 ms
platform.js
124 ms
ui.tabs.css
1197 ms
flexslider.css
1211 ms
public.css
1260 ms
jquery.form.min.js
1318 ms
scripts.js
1369 ms
xeory-postviews.js
1369 ms
widget.min.js
1225 ms
xeory-postviews.js
1302 ms
core.min.js
1301 ms
tabs.min.js
1292 ms
jquery.pagetop.js
1271 ms
postviews-cache.js
1257 ms
jquery.flexslider-min.js
1251 ms
jQuery.easing.min.js
1139 ms
jquery.fancybox-1.3.7.min.js
1270 ms
jquery.mousewheel.min.js
1247 ms
analytics.js
27 ms
logo4.png
532 ms
kv-01-900x270.png
1974 ms
kv-02-900x270.png
2385 ms
kv-03-900x270.png
1886 ms
kv-04-900x270.png
2061 ms
kv-05-900x270.png
2648 ms
kv-06-900x270.png
1824 ms
kv-07-900x270.png
2866 ms
kv-text.png
2067 ms
113.jpg
2363 ms
219-e1427418180854.jpg
2232 ms
110.jpg
2605 ms
1-200x200.jpg
2403 ms
1-200x200.jpg
2560 ms
110-200x200.jpg
2581 ms
1-200x200.jpg
2575 ms
112-200x200.jpg
2756 ms
1-200x200.jpg
2746 ms
112-200x200.jpg
2780 ms
110-200x200.jpg
2784 ms
116-200x200.jpg
2832 ms
114-200x200.jpg
2915 ms
113-200x200.jpg
2949 ms
110-200x200.jpg
2976 ms
1-200x200.jpg
2962 ms
128-200x200.jpg
3018 ms
sdk.js
13 ms
126-200x200.jpg
3022 ms
collect
44 ms
ico_bringup.png
2864 ms
1.jpg
3116 ms
1.jpg
3096 ms
110.jpg
3149 ms
116.jpg
2982 ms
collect
256 ms
ico_choose.png
2978 ms
fontawesome-webfont.woff
15 ms
110.jpg
3361 ms
323 ms
xd_arbiter.php
152 ms
xd_arbiter.php
166 ms
admin-ajax.php
3479 ms
1.jpg
2915 ms
112.jpg
3339 ms
page.php
128 ms
SjqsVDvTIBF.css
36 ms
AAMYCR68qe3.css
63 ms
_rx8naC75Dy.js
89 ms
3o1espZ6Mhb.js
113 ms
nfTYZZc0iSn.js
120 ms
pJPDNGWM_rf.js
137 ms
eJ-OD1MiSJg.js
116 ms
10599443_1524301854481453_1432301960991068364_n.jpg
134 ms
250 ms
185 ms
10177300_1444775232434116_5564380382078345427_n.png
12 ms
wL6VQj7Ab77.png
9 ms
s7jcwEQH7Sx.png
8 ms
b53Ajb4ihCP.gif
9 ms
R9a_DtVRZgv.js
3 ms
cUDgRFxaoIk.js
7 ms
0JBr1QHp8Gi.js
4 ms
kDOzhTr2W91.js
8 ms
css;base64,
1 ms
MKiDk2JIhZf.css
5 ms
SFuJyO56WQT.js
9 ms
lRyN50VcaFW.js
4 ms
182868_103261323086415_6173261_n.jpg
23 ms
safe_image.php
121 ms
safe_image.php
112 ms
safe_image.php
107 ms
safe_image.php
117 ms
safe_image.php
118 ms
12507640_634774853327656_8392686117862808936_n.jpg
102 ms
10547439_692329537528507_1862984267103974626_n.jpg
104 ms
10882360_675167352599835_7502810628105632641_n.jpg
116 ms
482132_107771232703579_1106894758_n.jpg
115 ms
12032245_1679745875596252_3347061572630357800_n.jpg
116 ms
427349_188743647926221_1926105211_n.jpg
115 ms
10603442_131773560528907_351030782586512236_n.jpg
107 ms
11903860_1031534873546127_1314773429586771284_n.jpg
115 ms
419866_179906398790375_30884878_n.jpg
113 ms
12208453_905970159486627_8263564440084720118_n.jpg
117 ms
11218975_141606006181603_2804428279338341228_n.jpg
119 ms
12074664_143078822710468_3771911577844666801_n.jpg
117 ms
LT9rONw9UJp.png
97 ms
AGUNXgX_Wx3.gif
37 ms
112.jpg
2305 ms
ico_display.png
1699 ms
1.jpg
2001 ms
masman.png
1724 ms
bg_foliage.png
2056 ms
bg_direction_nav.png
1752 ms
a-t-g.jp 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
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
a-t-g.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
a-t-g.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A-t-g.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 A-t-g.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.
a-t-g.jp
Open Graph data is detected on the main page of A T G. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: