Tools & Wizards About Us
welbe.co.jp screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

welbe.co.jp

障害者の就職支援ならウェルビー株式会社

Page Load Speed

18.7 sec in total

First Response

567 ms

Resources Loaded

9 sec

Page Rendered

9.2 sec

welbe.co.jp screenshot

About Website

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

ウェルビー株式会社は障害のある方々が、仕事を通じて「生きがい」と「希望」が持てる社会を目指し、お一人おひとりのペースや個性に合わせた様々な就職支援サービスを提供しています。

Visit welbe.co.jp

Key Findings

We analyzed Welbe.co.jp page load time and found that the first response time was 567 ms and then it took 18.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.

Performance Metrics

welbe.co.jp performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value23.3 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value7,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.552

13/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

welbe.co.jp

567 ms

welbe.co.jp

764 ms

www.welbe.co.jp

1964 ms

css

40 ms

normalize.css

198 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 58% of them (84 requests) were addressed to the original Welbe.co.jp, 3% (4 requests) were made to Px.ladsp.com and 1% (2 requests) were made to Discoveryplus.popin.cc. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Welbe.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 522.4 kB (5%)

Content Size

9.7 MB

After Optimization

9.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 79.3 kB

  • Original 94.9 kB
  • After minification 76.9 kB
  • After compression 15.5 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 18.0 kB, which is 19% 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 79.3 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 365.7 kB

  • Original 9.3 MB
  • After minification 9.0 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. Welbe images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 74.1 kB

  • Original 239.7 kB
  • After minification 226.8 kB
  • After compression 165.6 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 74.1 kB or 31% of the original size.

CSS Optimization

-15%

Potential reduce by 3.3 kB

  • Original 22.2 kB
  • After minification 22.2 kB
  • After compression 18.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. Welbe.co.jp needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (47%)

Requests Now

133

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

welbe.co.jp

welbe.co.jp

567 ms

welbe.co.jp

welbe.co.jp

764 ms

www.welbe.co.jp

www.welbe.co.jp

1964 ms

css

css

40 ms

normalize.css

normalize.css

198 ms

common.css

common.css

394 ms

swiper.min.css

swiper.min.css

583 ms

style.css

style.css

714 ms

top.css

top.css

718 ms

tag.js

tag.js

12 ms

sdk.js

sdk.js

25 ms

libs.js

libs.js

1130 ms

base.js

base.js

738 ms

swiper.min.js

swiper.min.js

1034 ms

index.js

index.js

1034 ms

ytag.js

ytag.js

728 ms

pixel.js

pixel.js

25 ms

analytics.js

analytics.js

362 ms

gtm.js

gtm.js

412 ms

tracking.js

tracking.js

1216 ms

uwt.js

uwt.js

397 ms

pb_pixel2.js

pb_pixel2.js

391 ms

header_logo.png

header_logo.png

314 ms

side_menu_01n_pc.png

side_menu_01n_pc.png

560 ms

side_menu_02n1_pc.png

side_menu_02n1_pc.png

559 ms

header_icon_08.png

header_icon_08.png

564 ms

modal_img_08.jpg

modal_img_08.jpg

849 ms

header_icon_01.png

header_icon_01.png

564 ms

modal_img_09.jpg

modal_img_09.jpg

596 ms

header_icon_07.png

header_icon_07.png

667 ms

modal_img_10.jpg

modal_img_10.jpg

669 ms

header_icon_02.png

header_icon_02.png

699 ms

modal_img_11.jpg

modal_img_11.jpg

701 ms

header_icon_03.png

header_icon_03.png

780 ms

modal_img_12.jpg

modal_img_12.jpg

1039 ms

header_icon_10.png

header_icon_10.png

859 ms

header_icon_04.png

header_icon_04.png

891 ms

modal_img_13.jpg

modal_img_13.jpg

895 ms

header_icon_09.png

header_icon_09.png

966 ms

side_menu_04n_pc.png

side_menu_04n_pc.png

1030 ms

side_menu_01_pc.png

side_menu_01_pc.png

1047 ms

side_menu_02n_pc.png

side_menu_02n_pc.png

1082 ms

mv_cm-movie2_pc.jpg

mv_cm-movie2_pc.jpg

1680 ms

mv_01_29_pc.jpg

mv_01_29_pc.jpg

1693 ms

mv_btn_01.png

mv_btn_01.png

1213 ms

mv_03_pc.jpg

mv_03_pc.jpg

1790 ms

mv_btn_03_pc.png

mv_btn_03_pc.png

1232 ms

mv_jobnavi06_pc.jpg

mv_jobnavi06_pc.jpg

2178 ms

wTikTok_pc.jpg

wTikTok_pc.jpg

1957 ms

voice_img_01n.png

voice_img_01n.png

1431 ms

voice_img_02n.png

voice_img_02n.png

1622 ms

voice_img_03n.png

voice_img_03n.png

1810 ms

banner_img_35_pc.jpg

banner_img_35_pc.jpg

1880 ms

banner_img_35_sp.jpg

banner_img_35_sp.jpg

1872 ms

pta.js

pta.js

383 ms

sdk.js

sdk.js

296 ms

banner_img_22n6_pc.jpg

banner_img_22n6_pc.jpg

2557 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

174 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

1 ms

banner_img_22n6_sp.jpg

banner_img_22n6_sp.jpg

1866 ms

banner_img_16_pc.jpg

banner_img_16_pc.jpg

1760 ms

206 ms

banner_img_16_sp.jpg

banner_img_16_sp.jpg

1743 ms

collect

collect

70 ms

banner_img_24_pc.jpg

banner_img_24_pc.jpg

1874 ms

banner_img_24_sp.jpg

banner_img_24_sp.jpg

1705 ms

support_img_01n.png

support_img_01n.png

1732 ms

support_img_02n1.png

support_img_02n1.png

1978 ms

rt.track.js

rt.track.js

878 ms

support_img_03n.png

support_img_03n.png

1801 ms

adsct

adsct

124 ms

adsct

adsct

107 ms

support_img_04n.png

support_img_04n.png

1864 ms

step_img_01n.png

step_img_01n.png

1838 ms

step_img_02n1.png

step_img_02n1.png

2019 ms

step_img_03n.png

step_img_03n.png

2064 ms

step_img_04n1.png

step_img_04n1.png

1964 ms

tiktok_bnr2.jpg

tiktok_bnr2.jpg

1917 ms

recommend_img_01.jpg

recommend_img_01.jpg

1879 ms

recommend_img_02.jpg

recommend_img_02.jpg

1992 ms

recommend_img_03_3.jpg

recommend_img_03_3.jpg

1957 ms

footer_img01.png

footer_img01.png

1984 ms

footer_img01.png

footer_img01.png

1925 ms

pixel

pixel

222 ms

footer_img02.png

footer_img02.png

1889 ms

footer_img02.png

footer_img02.png

1923 ms

logo2_welbe_w.svg

logo2_welbe_w.svg

1990 ms

to-top.png

to-top.png

1963 ms

pixel

pixel

146 ms

iframe

iframe

187 ms

tracking.js

tracking.js

1289 ms

header_icon_ir.png

header_icon_ir.png

1850 ms

jobnavi_white_logo.png

jobnavi_white_logo.png

1848 ms

iframe

iframe

352 ms

rt.track.js

rt.track.js

374 ms

Pug

Pug

134 ms

hs

hs

768 ms

sync.ad-stir.com

sync.ad-stir.com

626 ms

tap.php

tap.php

136 ms

sync

sync

860 ms

146 ms

cookiesync

cookiesync

620 ms

cs

cs

745 ms

sync.ad

sync.ad

300 ms

cs

cs

721 ms

sync

sync

299 ms

sync

sync

132 ms

icn_arw_y.svg

icn_arw_y.svg

1670 ms

tap.php

tap.php

57 ms

sync

sync

201 ms

sync.ad

sync.ad

214 ms

cs

cs

760 ms

cs

cs

699 ms

sync.ad-stir.com

sync.ad-stir.com

659 ms

Pug

Pug

49 ms

cookiesync

cookiesync

608 ms

53 ms

hs

hs

800 ms

bounce

bounce

18 ms

pixel

pixel

23 ms

sd

sd

10 ms

google

google

150 ms

bounce

bounce

9 ms

sync

sync

17 ms

sd

sd

6 ms

google

google

165 ms

sync

sync

15 ms

btn_icn1.png

btn_icn1.png

1529 ms

sync

sync

2 ms

btn_icn2.png

btn_icn2.png

1543 ms

btn_icn3.png

btn_icn3.png

1542 ms

period_img01n.jpg

period_img01n.jpg

1641 ms

sec_04_bg.png

sec_04_bg.png

1461 ms

center_bg.png

center_bg.png

2139 ms

voice_bg.png

voice_bg.png

1498 ms

v_next_icon.png

v_next_icon.png

1451 ms

v_prev_icon.png

v_prev_icon.png

1358 ms

logo_habii.svg

logo_habii.svg

1374 ms

logo_ilis_w.png

logo_ilis_w.png

1402 ms

logo_hapi_dig_w.svg

logo_hapi_dig_w.svg

1413 ms

icn_fb.png

icn_fb.png

1359 ms

x-gm-ttr-api-redirect-location

x-gm-ttr-api-redirect-location

1170 ms

scenario.js

scenario.js

202 ms

access

access

1060 ms

scenario.js

scenario.js

1053 ms

Accessibility Review

welbe.co.jp accessibility score

91

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

welbe.co.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

welbe.co.jp SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Welbe.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 Welbe.co.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.

Social Sharing Optimization

welbe.co.jp

Open Graph data is detected on the main page of Welbe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: