Tools & Wizards About Us
weblab.co.jp screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

weblab.co.jp

Web制作会社 東京 | Webマーケティング支援・集客サイト制作のウェブラボ株式会社

Page Load Speed

10.3 sec in total

First Response

512 ms

Resources Loaded

8.9 sec

Page Rendered

886 ms

weblab.co.jp screenshot

About Website

Welcome to weblab.co.jp homepage info - get ready to check Web Lab best content for Japan right away, or after learning these important things about weblab.co.jp

東京のWeb制作会社ウェブラボ。単なるホームページ制作だけでなく、Webマーケティングで貴社の事業成長を支援します。2004年の創業以来、20年以上の実績。上場企業から中小企業まで、集客や採用の課題を解決へと導くパートナーとしてご相談ください。

Visit weblab.co.jp

Key Findings

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

Performance Metrics

weblab.co.jp performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

38/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value730 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.278

44/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

weblab.co.jp

512 ms

www.weblab.co.jp

1579 ms

gtm.js

77 ms

top.css

517 ms

logo.svg

609 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 98% of them (58 requests) were addressed to the original Weblab.co.jp, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Weblab.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.7 kB (6%)

Content Size

978.5 kB

After Optimization

918.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weblab.co.jp main page is 978.5 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. 30% of websites need less resources to load. Images take 890.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 30.1 kB

  • Original 39.4 kB
  • After minification 34.4 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 5.1 kB, which is 13% 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 30.1 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 19.8 kB

  • Original 890.7 kB
  • After minification 870.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. Web Lab images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 5.3 kB

  • Original 37.5 kB
  • After minification 37.5 kB
  • After compression 32.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 5.3 kB or 14% of the original size.

CSS Optimization

-42%

Potential reduce by 4.6 kB

  • Original 10.9 kB
  • After minification 10.9 kB
  • After compression 6.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. Weblab.co.jp needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (5%)

Requests Now

57

After Optimization

54

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weblab.co.jp

weblab.co.jp

512 ms

www.weblab.co.jp

www.weblab.co.jp

1579 ms

gtm.js

gtm.js

77 ms

top.css

top.css

517 ms

logo.svg

logo.svg

609 ms

main01.jpg

main01.jpg

2234 ms

img_top_works_saison-am_fund_app.jpg

img_top_works_saison-am_fund_app.jpg

883 ms

img_top_works_ardor-ts.jpg

img_top_works_ardor-ts.jpg

888 ms

img_top_works_tokyo-cci.jpg

img_top_works_tokyo-cci.jpg

923 ms

img_top_works_mtfuji-hotel.jpg

img_top_works_mtfuji-hotel.jpg

1366 ms

img_top_works_39asset.jpg

img_top_works_39asset.jpg

1236 ms

img_top_works_hasuo-ts.jpg

img_top_works_hasuo-ts.jpg

1546 ms

img_top_works_dr-head.jpg

img_top_works_dr-head.jpg

2204 ms

img_top_works_fujiyakuhin.jpg

img_top_works_fujiyakuhin.jpg

1613 ms

img_top_works_aoki.jpg

img_top_works_aoki.jpg

1905 ms

img_top_works_fujiyamastyle2022.jpg

img_top_works_fujiyamastyle2022.jpg

1906 ms

img_top_works_masudajuku_re.jpg

img_top_works_masudajuku_re.jpg

2266 ms

img_top_works_jraia_or.jpg

img_top_works_jraia_or.jpg

2356 ms

img_top_itw_roukin.jpg

img_top_itw_roukin.jpg

2584 ms

img_top_itw_saison.jpg

img_top_itw_saison.jpg

2624 ms

img_top_itw_highland.jpg

img_top_itw_highland.jpg

2920 ms

img_top_service01.png

img_top_service01.png

2781 ms

img_top_service03.png

img_top_service03.png

2792 ms

img_top_service04.png

img_top_service04.png

2893 ms

img_top_service12.png

img_top_service12.png

3081 ms

img_top_service02.png

img_top_service02.png

3152 ms

img_top_service06.png

img_top_service06.png

3279 ms

img_top_service09.png

img_top_service09.png

3320 ms

img_top_service07.png

img_top_service07.png

3429 ms

img_top_service11.png

img_top_service11.png

3433 ms

img_top_service14.png

img_top_service14.png

3576 ms

img_top_service05.png

img_top_service05.png

3648 ms

img_top_service10.png

img_top_service10.png

3805 ms

img_top_service08.png

img_top_service08.png

3843 ms

bnr_5point.png

bnr_5point.png

4115 ms

bnr_sheet.png

bnr_sheet.png

4285 ms

d_eye_202404-300x200.jpg

d_eye_202404-300x200.jpg

4279 ms

d_eye_20240424-300x200.jpg

d_eye_20240424-300x200.jpg

4538 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

4631 ms

common.js

common.js

3791 ms

top.js

top.js

4024 ms

d_eye_20240418-300x200.jpg

d_eye_20240418-300x200.jpg

4922 ms

d_eye_20240411-300x202.jpg

d_eye_20240411-300x202.jpg

5523 ms

d_eye_20240404-300x225.jpg

d_eye_20240404-300x225.jpg

4004 ms

d_eye_20240328-300x200.jpg

d_eye_20240328-300x200.jpg

4130 ms

img_top_recruit.jpg

img_top_recruit.jpg

4340 ms

bnr_google_partner.gif

bnr_google_partner.gif

3633 ms

bnr_yahoo_partner.gif

bnr_yahoo_partner.gif

3836 ms

bnr_ajsa.gif

bnr_ajsa.gif

3804 ms

bnr_gsl.gif

bnr_gsl.gif

3985 ms

f_logo.svg

f_logo.svg

3749 ms

ico_h_cv.png

ico_h_cv.png

3981 ms

arw_w.png

arw_w.png

3947 ms

ico_blank_w.png

ico_blank_w.png

3960 ms

bg_f_cv.gif

bg_f_cv.gif

3830 ms

ico_tel.png

ico_tel.png

3826 ms

ico_mail_w.png

ico_mail_w.png

3938 ms

ico_fb.png

ico_fb.png

2034 ms

ico_tw.png

ico_tw.png

2158 ms

Accessibility Review

weblab.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.

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

Best Practices

weblab.co.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

weblab.co.jp SEO score

83

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

High

robots.txt is not valid

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 Weblab.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 Weblab.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

weblab.co.jp

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