33.6 sec in total
518 ms
25.8 sec
7.3 sec
Welcome to green-arrow.jp homepage info - get ready to check Green Arrow best content for Japan right away, or after learning these important things about green-arrow.jp
グリーンアローは千葉を中心に東京、茨城エリア(津田沼・八千代・海浜幕張・新小岩・蘇我・船橋・柏・袖ケ浦・浅草吾妻橋・ららぽーとTOKYO-BAY・つくば)でボルダリング&クライミング&トランポリンパークを運営しています。 経験者はもちろん、初めての方にもクライミングやトランポリンを通じて、皆様に成長を楽しめるスポーツのコミュニティパークを提供いたします。 また、クライミングの専門知識を有する社員が...
Visit green-arrow.jpWe analyzed Green-arrow.jp page load time and found that the first response time was 518 ms and then it took 33.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 22 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
green-arrow.jp performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value56.6 s
0/100
25%
Value16.7 s
0/100
10%
Value6,030 ms
0/100
30%
Value0.457
19/100
15%
Value15.8 s
6/100
10%
518 ms
868 ms
179 ms
34 ms
332 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 65% of them (102 requests) were addressed to the original Green-arrow.jp, 8% (13 requests) were made to Maps.googleapis.com and 8% (12 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Green-arrow.jp.
Page size can be reduced by 642.0 kB (28%)
2.3 MB
1.6 MB
In fact, the total size of Green-arrow.jp main page is 2.3 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 1.4 MB which makes up the majority of the site volume.
Potential reduce by 55.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. 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 55.3 kB or 81% of the original size.
Potential reduce by 165.6 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, Green Arrow needs image optimization as it can save up to 165.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 372.8 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 372.8 kB or 49% of the original size.
Potential reduce by 48.3 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. Green-arrow.jp needs all CSS files to be minified and compressed as it can save up to 48.3 kB or 71% of the original size.
Number of requests can be reduced by 58 (47%)
123
65
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Green Arrow. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
green-arrow.jp
518 ms
www.green-arrow.jp
868 ms
all.css
179 ms
css
34 ms
import.css
332 ms
lower.less
340 ms
mt.js
510 ms
cube.site.js
342 ms
cube.win_op.js
346 ms
jquery-1.8.3.min.js
19 ms
jquery.easing.1.3.js
674 ms
slick.js
1335 ms
jquery.mousewheel.js
683 ms
jquery.rollOver.js
691 ms
jquery.slideImage.js
688 ms
jquery.fullSlide.js
854 ms
jquery.customScroll.js
1020 ms
jquery.droppy.js
1040 ms
fixHeight.js
1037 ms
jquery.nicescroll.js
1745 ms
shadowbox.js
1530 ms
js
42 ms
config.js.php
1355 ms
ga.js
1377 ms
kitchen.juicer.cc
309 ms
kitchen.juicer.cc
571 ms
base.css
1048 ms
content.css
1506 ms
dmanager.css
1359 ms
shop.css
1393 ms
shop-other.css
1400 ms
shadowbox.css
1539 ms
extra.css
1702 ms
w_js.php
1848 ms
bookmark_button.js
6 ms
bookmark_button.js
11 ms
gen_204
99 ms
analytics.js
95 ms
embed
209 ms
bg.jpg
541 ms
scroll01-bg.png
179 ms
scroll02-bg.png
417 ms
scroll03-bg.png
678 ms
scroll04-bg.png
417 ms
logo.png
848 ms
header-nav01.jpg
579 ms
2022125115242.jpg
922 ms
header-nav02.jpg
753 ms
header-nav03.jpg
856 ms
gnav01.jpg
909 ms
gnav02.jpg
1015 ms
gnav03.jpg
1086 ms
gnav04.jpg
1195 ms
gnav05.jpg
1193 ms
gnav06.jpg
1253 ms
slideshow-prev.png
1257 ms
slideshow-next.png
1346 ms
data-220424112524.PNG
8085 ms
data-220425171419.PNG
10947 ms
data-220424112615.PNG
8901 ms
data-220424112628.PNG
11276 ms
data-220424112638.PNG
8772 ms
data-220424112649.PNG
8345 ms
data-220424112659.PNG
16610 ms
data-220424112711.PNG
14357 ms
data-220424112727.PNG
19877 ms
youtube%E3%82%B9%E3%83%9E%E3%83%9B%E3%83%90%E3%83%8A%E3%83%BCGA20220620%282%29.png
12721 ms
%E4%BC%9A%E5%93%A1%E7%99%BB%E9%8C%B2%E3%83%90%E3%83%8A%E3%83%BC20220830%281%29.png
12510 ms
data-210624170047.JPG
19877 ms
data-220424113702.JPG
19878 ms
data-210624171500.JPG
19878 ms
data-220426111410.JPG
19879 ms
data-200225215658.JPG
19879 ms
data-200225215713.JPG
19806 ms
data-200225215733.JPG
19805 ms
u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwQ.woff
99 ms
collect
99 ms
plusone.js
117 ms
widgets.js
125 ms
fa-regular-400.woff
63 ms
fa-solid-900.woff
232 ms
data-211230174646.JPG
19705 ms
rs=ABjfnFXDiAwoNRBDvr7RbL_Dlwhxvi8fNQ
38 ms
css
17 ms
js
38 ms
m=gmeviewer_base
77 ms
cb=gapi.loaded_0
61 ms
widget_iframe.7dae38096d06923d683a2a807172322a.html
266 ms
gen_204
133 ms
lazy.min.js
95 ms
m=ws9Tlc
99 ms
common.js
88 ms
util.js
101 ms
map.js
94 ms
overlay.js
95 ms
1899-blank-shape_pin_4x.png&highlight=ff000000,0F9D58&scale=2.0
120 ms
marker.js
91 ms
geocoder.js
86 ms
controls.js
87 ms
places_impl.js
112 ms
selection_2x-000.png
75 ms
1899-blank-shape_pin_4x.png&highlight=ff000000,4E342E&scale=2.0
114 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
49 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
67 ms
KFOmCnqEu92Fr1Mu4mxM.woff
68 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
67 ms
gen204
91 ms
info-000.png
41 ms
gm-close000.png
41 ms
data-220424113522.JPG
20467 ms
data-220426111128.JPG
20466 ms
settings
83 ms
openhand_8_8.cur
49 ms
onion.js
22 ms
data-211109162508.JPG
20329 ms
transparent.png
11 ms
data-220424114014.JPG
20301 ms
mainbn1-1.png
19574 ms
mainbn1-2.png
19509 ms
mainbn1-3.png
19755 ms
main-carousel-title2.png
19758 ms
data-200227111653.jpg
19974 ms
data-200227112315.jpg
19962 ms
data-220424114555.jpg
19869 ms
data-200227111718.jpg
19798 ms
data-200227111736.jpg
19691 ms
data-200420121145.jpg
19690 ms
data-211230175123.jpg
19632 ms
data-220424114401.jpg
19627 ms
climb-bg.png
19537 ms
viewer-icons001.png
45 ms
MyMaps_Icons003.png
15 ms
mymaps_32.png
16 ms
v1_4593b7d7.png
16 ms
google-my-maps-logo-small-001.png
14 ms
stats.js
6 ms
common.js
6 ms
util.js
14 ms
2020-04-20-12-19-18.jpg
13321 ms
2020-04-20-12-13-50.jpg
13053 ms
2020-04-20-12-22-23.jpg
13157 ms
2018-06-01-18-58-50.jpg
12544 ms
2020-04-20-12-16-29.jpg
10650 ms
mainbn2-1.png
10013 ms
mainbn2-2.png
9134 ms
mainbn2-3.png
9032 ms
mainbn2-4.png
7406 ms
mainbn2-5.png
5193 ms
mainbn2-6.png
2072 ms
fnav01.jpg
2113 ms
fnav02.jpg
2216 ms
fnav03.jpg
2226 ms
fnav04.jpg
2267 ms
fnav05.jpg
2408 ms
fnav06.jpg
2420 ms
fnav08.jpg
2648 ms
pagetop2.png
2558 ms
2354 ms
green-arrow.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
Links do not have a discernible name
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>).
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.
green-arrow.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
green-arrow.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 doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Green-arrow.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 Green-arrow.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.
green-arrow.jp
Open Graph description is not detected on the main page of Green Arrow. 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: