5.1 sec in total
527 ms
4.1 sec
471 ms
Visit goorilla.jp now to see the best up-to-date Goorilla content and also check out these interesting facts you probably never knew about goorilla.jp
Goorilla株式会社のコーポレートサイトです。「人が『輝く』環境を。」を理念にHR事業を展開しております。人が本当に輝くのに必要なことは「自信を持つこと」です。Goorillaは企業と求職者を本当の意味でマッチングすることでのお手伝いをさせて頂きます。
Visit goorilla.jpWe analyzed Goorilla.jp page load time and found that the first response time was 527 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
goorilla.jp performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value30.6 s
0/100
25%
Value8.1 s
21/100
10%
Value1,070 ms
25/100
30%
Value0.001
100/100
15%
Value10.3 s
25/100
10%
527 ms
1091 ms
174 ms
513 ms
669 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 53% of them (26 requests) were addressed to the original Goorilla.jp, 35% (17 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Goorilla.jp.
Page size can be reduced by 56.6 kB (7%)
865.1 kB
808.4 kB
In fact, the total size of Goorilla.jp main page is 865.1 kB. 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 723.0 kB which makes up the majority of the site volume.
Potential reduce by 36.7 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 36.7 kB or 77% of the original size.
Potential reduce by 5.9 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. Goorilla images are well optimized though.
Potential reduce by 4.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. This website has mostly compressed JavaScripts.
Potential reduce by 9.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. Goorilla.jp needs all CSS files to be minified and compressed as it can save up to 9.7 kB or 25% of the original size.
Number of requests can be reduced by 22 (76%)
29
7
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Goorilla. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
goorilla.jp
527 ms
goorilla.jp
1091 ms
wp-emoji-release.min.js
174 ms
style.css
513 ms
responsive-pc.css
669 ms
font-awesome.min.css
685 ms
style.css
687 ms
extension.css
768 ms
style.css
773 ms
pagenavi-css.css
772 ms
jquery.js
1022 ms
jquery-migrate.min.js
862 ms
main.css
863 ms
javascript.js
966 ms
javascript.js
969 ms
wp-embed.min.js
970 ms
rAF-polyfil.js
1042 ms
jquery.lazylinepainter-1.7.0.min.js
1042 ms
svgdata.js
1178 ms
topSVG.js
1179 ms
question.js
1179 ms
widget.js
99 ms
notosansjapanese.css
30 ms
css
46 ms
sdk.js
139 ms
img_header_logo-1.png
202 ms
bg_top_rake.jpg
873 ms
bg_top_service.jpg
693 ms
bg_top_recruit.jpg
1227 ms
NotoSansJP-Light.woff
75 ms
NotoSansJP-Thin.woff
130 ms
NotoSansJP-DemiLight.woff
159 ms
NotoSansJP-Regular.woff
226 ms
NotoSansJP-Medium.woff
225 ms
NotoSansJP-Bold.woff
224 ms
NotoSansJP-Black.woff
158 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff
155 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQUwaEQXjN_mQ.woff
156 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4vaVQUwaEQXjN_mQ.woff
155 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B5OaVQUwaEQXjN_mQ.woff
159 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B5caVQUwaEQXjN_mQ.woff
161 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4iaVQUwaEQXjN_mQ.woff
159 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4jaVQUwaEQXjN_mQ.woff
160 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4saVQUwaEQXjN_mQ.woff
219 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQUwaEQXjN_mQ.woff
220 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVQUwaEQXjN_mQ.woff
219 ms
sdk.js
5 ms
152 ms
print.css
174 ms
goorilla.jp accessibility score
goorilla.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
goorilla.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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Goorilla.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 Goorilla.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.
goorilla.jp
Open Graph data is detected on the main page of Goorilla. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: