Tools & Wizards About Us
braves.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

braves.co.jp

【公式】ブレイブ｜看護・介護・保育士・薬剤師・コールセンター・事務の派遣・転職の求人情報サイト

Page Load Speed

9.4 sec in total

First Response

498 ms

Resources Loaded

8.6 sec

Page Rendered

275 ms

braves.co.jp screenshot

About Website

Visit braves.co.jp now to see the best up-to-date Braves content for Japan and also check out these interesting facts you probably never knew about braves.co.jp

看護・介護・保育士・薬剤師・コールセンター・事務の人材派遣・転職の求人なら、マイナビグループのブレイブ。日々更新される最新の求人情報から看護師・介護士・保育士・薬剤師やコールセンター・事務の派遣や正社員の求人が検索できます。

Visit braves.co.jp

Key Findings

We analyzed Braves.co.jp page load time and found that the first response time was 498 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

braves.co.jp performance score

0

Network Requests Diagram

braves.co.jp

498 ms

www.braves.co.jp

1963 ms

jquery-1.8.2.min.js

1408 ms

custom.js

362 ms

main.css

362 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 88% of them (76 requests) were addressed to the original Braves.co.jp, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Braves.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.8 kB (17%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Braves.co.jp main page is 1.6 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. 25% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 32.9 kB

  • Original 41.8 kB
  • After minification 34.8 kB
  • After compression 8.9 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 7.0 kB, which is 17% 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 32.9 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 50.2 kB

  • Original 1.3 MB
  • After minification 1.2 MB

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. Braves images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 110.9 kB

  • Original 196.6 kB
  • After minification 169.6 kB
  • After compression 85.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 110.9 kB or 56% of the original size.

CSS Optimization

-84%

Potential reduce by 76.8 kB

  • Original 91.7 kB
  • After minification 62.5 kB
  • After compression 14.9 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. Braves.co.jp needs all CSS files to be minified and compressed as it can save up to 76.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (46%)

Requests Now

82

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Braves. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

braves.co.jp

braves.co.jp

498 ms

www.braves.co.jp

www.braves.co.jp

1963 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

1408 ms

custom.js

custom.js

362 ms

main.css

main.css

362 ms

utils.js

utils.js

1019 ms

ajax_utils.js

ajax_utils.js

802 ms

jobtype.js

jobtype.js

538 ms

route.js

route.js

715 ms

distcode.js

distcode.js

537 ms

station.js

station.js

605 ms

index.js

index.js

928 ms

checkLogin.js

checkLogin.js

716 ms

ssl.js

ssl.js

416 ms

conversion.js

conversion.js

22 ms

s_retargeting.js

s_retargeting.js

576 ms

base.css

base.css

378 ms

font.css

font.css

182 ms

top.css

top.css

535 ms

sub.css

sub.css

179 ms

search.css

search.css

193 ms

mypage.css

mypage.css

195 ms

free.css

free.css

354 ms

detail.css

detail.css

359 ms

present.css

present.css

382 ms

cross.css

cross.css

575 ms

mail_box.css

mail_box.css

530 ms

scout.css

scout.css

537 ms

relation.css

relation.css

563 ms

analytics.js

analytics.js

80 ms

h1_bg.gif

h1_bg.gif

192 ms

logo.gif

logo.gif

184 ms

tel.png

tel.png

182 ms

arrow.gif

arrow.gif

181 ms

business.png

business.png

193 ms

list_bg.png

list_bg.png

195 ms

top_image_bg.png

top_image_bg.png

358 ms

kango_btn.png

kango_btn.png

357 ms

kaigo_btn.png

kaigo_btn.png

538 ms

hoiku_btn.png

hoiku_btn.png

376 ms

call_btn.png

call_btn.png

383 ms

kango.png

kango.png

4680 ms

kaigo.png

kaigo.png

1628 ms

hoiku.png

hoiku.png

2329 ms

call.png

call.png

1708 ms

map_search_bg.jpg

map_search_bg.jpg

4178 ms

hokkaido_btn.png

hokkaido_btn.png

718 ms

kanto_btn.png

kanto_btn.png

900 ms

tokai_btn.png

tokai_btn.png

1080 ms

kansai_btn.png

kansai_btn.png

1261 ms

chugoku_btn.png

chugoku_btn.png

1442 ms

kyusyu_btn.png

kyusyu_btn.png

1623 ms

hideAreaBg01.png

hideAreaBg01.png

1807 ms

hideAreaTop01.png

hideAreaTop01.png

1803 ms

closed.png

closed.png

1896 ms

hideAreaBg03.png

hideAreaBg03.png

1981 ms

hideAreaTop03.png

hideAreaTop03.png

1985 ms

hideAreaBg04.png

hideAreaBg04.png

2087 ms

hideAreaTop04.png

hideAreaTop04.png

2157 ms

hideAreaBg05.png

hideAreaBg05.png

2160 ms

hideAreaTop05.png

hideAreaTop05.png

2271 ms

hideAreaBg06.png

hideAreaBg06.png

2329 ms

hideAreaTop06.png

hideAreaTop06.png

2339 ms

freeSearchBtn.png

freeSearchBtn.png

2460 ms

search.jpg

search.jpg

2495 ms

attention.jpg

attention.jpg

2813 ms

85 ms

collect

collect

4 ms

collect

collect

71 ms

gtm.js

gtm.js

49 ms

43 ms

19 ms

easy_search.jpg

easy_search.jpg

2710 ms

registBtn.png

registBtn.png

2483 ms

banner2.jpg

banner2.jpg

3109 ms

23 ms

bPoint.jpg

bPoint.jpg

3048 ms

banner01.jpg

banner01.jpg

3029 ms

banner02.jpg

banner02.jpg

2878 ms

banner03.jpg

banner03.jpg

3074 ms

fukuri.jpg

fukuri.jpg

3218 ms

ccaj.jpg

ccaj.jpg

3428 ms

jassa.jpg

jassa.jpg

4012 ms

privacy02.gif

privacy02.gif

3074 ms

B0969314.gif

B0969314.gif

3032 ms

page_top.png

page_top.png

2888 ms

SEO Factors

braves.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT-JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Braves.co.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 Braves.co.jp main page’s claimed encoding is shift-jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

braves.co.jp

Open Graph description is not detected on the main page of Braves. 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: