Tools & Wizards About Us
levtech.jp screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

levtech.jp

【公式】レバテック｜ITの仕事さがしはレバテック

Page Load Speed

3.7 sec in total

First Response

10 ms

Resources Loaded

2.8 sec

Page Rendered

853 ms

levtech.jp screenshot

About Website

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

登録者数45万人以上・業界認知度No.1・リピート率90%以上・大手からベンチャーまで求人多数！技術トレンドだけでなく業界トレンドにも詳しいIT専門の担当者が、あなたの仕事さがしをサポートします！

Visit levtech.jp

Key Findings

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

Performance Metrics

levtech.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value89.5 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value5,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.0 s

1/100

10%

Network Requests Diagram

levtech.jp

10 ms

levtech.jp

999 ms

25666110737.js

74 ms

browserMonitoringPrd.js

882 ms

css2

57 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 74% of them (46 requests) were addressed to the original Levtech.jp, 10% (6 requests) were made to Lt-prd-ownd-images.s3.ap-northeast-1.amazonaws.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Levtech.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.4 kB (76%)

Content Size

177.9 kB

After Optimization

42.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Levtech.jp main page is 177.9 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. 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. HTML takes 168.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 135.4 kB

  • Original 168.1 kB
  • After minification 167.8 kB
  • After compression 32.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 135.4 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 9.6 kB
  • After minification 9.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. Levtech images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 48 B

  • Original 225 B
  • After minification 225 B
  • After compression 177 B

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 48 B or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (25%)

Requests Now

56

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Levtech. 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 from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

levtech.jp

levtech.jp

10 ms

levtech.jp

levtech.jp

999 ms

25666110737.js

25666110737.js

74 ms

browserMonitoringPrd.js

browserMonitoringPrd.js

882 ms

css2

css2

57 ms

css2

css2

158 ms

geo4.js

geo4.js

64 ms

gtm.js

gtm.js

99 ms

entry.PY-Jk8aq.css

entry.PY-Jk8aq.css

27 ms

index.Bwcn8gP1.css

index.Bwcn8gP1.css

19 ms

FloatingCta.DGNJcNmK.css

FloatingCta.DGNJcNmK.css

38 ms

ToEfButtonForTop.CHAsgBxA.css

ToEfButtonForTop.CHAsgBxA.css

23 ms

SellingPointOfRookie.BJeMporN.css

SellingPointOfRookie.BJeMporN.css

26 ms

IconBase.qmft8XA7.css

IconBase.qmft8XA7.css

27 ms

LabCardAreaSp.BpjJe_Z9.css

LabCardAreaSp.BpjJe_Z9.css

30 ms

MainMenuSp.49bngqgO.css

MainMenuSp.49bngqgO.css

42 ms

RegionArea.BBkpDVZy.css

RegionArea.BBkpDVZy.css

57 ms

RichFooter.mlnJ8jTq.css

RichFooter.mlnJ8jTq.css

40 ms

logo_lt.svg

logo_lt.svg

625 ms

logo_ltf.svg

logo_ltf.svg

621 ms

logo_ltcr.svg

logo_ltcr.svg

631 ms

logo_ltc.svg

logo_ltc.svg

636 ms

logo_ltd.svg

logo_ltd.svg

664 ms

logo_lt_type.svg

logo_lt_type.svg

631 ms

logo_levtech_header.l7tlALP4.svg

logo_levtech_header.l7tlALP4.svg

137 ms

logo_lab.BdcYSExo.svg

logo_lab.BdcYSExo.svg

143 ms

image_kv_kaku.dRK27q59.webp

image_kv_kaku.dRK27q59.webp

132 ms

image_description.B0uag_kv.webp

image_description.B0uag_kv.webp

132 ms

image_achievement_01.DhB-o8_k.svg

image_achievement_01.DhB-o8_k.svg

132 ms

image_achievement_02.Du6-dPbv.svg

image_achievement_02.Du6-dPbv.svg

141 ms

image_achievement_03.DuL17XSJ.svg

image_achievement_03.DuL17XSJ.svg

134 ms

image_service_tab_01.C75ds3A0.svg

image_service_tab_01.C75ds3A0.svg

137 ms

image_achievement_freelance_01.UCR7zJb_.svg

image_achievement_freelance_01.UCR7zJb_.svg

909 ms

image_achievement_freelance_02.BoN9k62o.svg

image_achievement_freelance_02.BoN9k62o.svg

902 ms

image_achievement_freelance_03.CS2JXbW2.svg

image_achievement_freelance_03.CS2JXbW2.svg

935 ms

image_selling_point_freelance_first.Oel12blf.svg

image_selling_point_freelance_first.Oel12blf.svg

985 ms

image_selling_point_freelance_second_01.BXsl1jPO.webp

image_selling_point_freelance_second_01.BXsl1jPO.webp

142 ms

image_selling_point_freelance_second_02.DyK4bLMt.webp

image_selling_point_freelance_second_02.DyK4bLMt.webp

143 ms

image_achievement_career_01.DkCNHGmF.svg

image_achievement_career_01.DkCNHGmF.svg

922 ms

image_achievement_career_02.Bcv4d-MM.svg

image_achievement_career_02.Bcv4d-MM.svg

1455 ms

image_achievement_career_03.BzRgTmkv.svg

image_achievement_career_03.BzRgTmkv.svg

1646 ms

image_selling_point_career_first.DZ6oJMrL.webp

image_selling_point_career_first.DZ6oJMrL.webp

919 ms

image_selling_point_career_second.DUDF2OST.webp

image_selling_point_career_second.DUDF2OST.webp

919 ms

image_selling_point_career_third.DkQKcyc3.webp

image_selling_point_career_third.DkQKcyc3.webp

920 ms

image_selling_point_career_fourth.ZiWLQaEw.webp

image_selling_point_career_fourth.ZiWLQaEw.webp

930 ms

image_selling_point_direct_first.8vdyIzbc.webp

image_selling_point_direct_first.8vdyIzbc.webp

932 ms

image_selling_point_direct_second.C5MkvJ7K.webp

image_selling_point_direct_second.C5MkvJ7K.webp

931 ms

image_selling_point_direct_third.BvtzUZDk.webp

image_selling_point_direct_third.BvtzUZDk.webp

940 ms

image_selling_point_direct_fourth.DLdidbqH.webp

image_selling_point_direct_fourth.DLdidbqH.webp

941 ms

image_achievement_rookie_01.DdIUz6pc.svg

image_achievement_rookie_01.DdIUz6pc.svg

1809 ms

image_achievement_rookie_02.CrDQowIg.svg

image_achievement_rookie_02.CrDQowIg.svg

1111 ms

image_selling_point_rookie_first.uLmo-oHT.webp

image_selling_point_rookie_first.uLmo-oHT.webp

941 ms

image_selling_point_rookie_second.C0JpyZLT.webp

image_selling_point_rookie_second.C0JpyZLT.webp

941 ms

image_region.BvyhknQD.webp

image_region.BvyhknQD.webp

941 ms

image_rich_footer.D_wHIggz.webp

image_rich_footer.D_wHIggz.webp

976 ms

pmark_200.png

pmark_200.png

1127 ms

image_mascot_yagi.BX_dK1FQ.webp

image_mascot_yagi.BX_dK1FQ.webp

985 ms

a25668240044.html

a25668240044.html

94 ms

KFOlCnqEu92Fr1MmWUlvAA.woff

KFOlCnqEu92Fr1MmWUlvAA.woff

40 ms

KFOmCnqEu92Fr1Me5g.woff

KFOmCnqEu92Fr1Me5g.woff

96 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75g.woff

138 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75g.woff

150 ms

Accessibility Review

levtech.jp accessibility score

83

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

Image elements do not have [alt] attributes

Best Practices

levtech.jp best practices score

83

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

levtech.jp SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

levtech.jp

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