Tools & Wizards About Us
lancers.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lancers.jp

ランサーズ | 日本最大級のクラウドソーシング・仕事依頼サイト

Page Load Speed

8 sec in total

First Response

362 ms

Resources Loaded

5.2 sec

Page Rendered

2.4 sec

lancers.jp screenshot

About Website

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

日本最大級のクラウドソーシング、ランサーズ。「エンジニアとデザイナー、ライターの登録者数は業界屈指！」 ホームページ制作、ロゴ作成などのデザイン、アプリ開発、システム開発、ライティング、単純作業などの仕事を、いつでもプロに依頼できます。

Visit lancers.jp

Key Findings

We analyzed Lancers.jp page load time and found that the first response time was 362 ms and then it took 7.6 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

lancers.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value5,900 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value32.4 s

0/100

10%

Network Requests Diagram

lancers.jp

362 ms

www.lancers.jp

1051 ms

css2

52 ms

rebranding.min.css

212 ms

faq-modal.min.css

40 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Lancers.jp, 43% (57 requests) were made to Static.lancers.jp and 8% (11 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Static.lancers.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 519.4 kB (26%)

Content Size

2.0 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lancers.jp main page is 2.0 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. 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. Javascripts take 909.9 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 384.6 kB

  • Original 438.5 kB
  • After minification 240.9 kB
  • After compression 53.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 197.6 kB, which is 45% 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 384.6 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 15.0 kB

  • Original 647.8 kB
  • After minification 632.8 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. Lancers images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 119.4 kB

  • Original 909.9 kB
  • After minification 909.5 kB
  • After compression 790.5 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 119.4 kB or 13% of the original size.

CSS Optimization

-2%

Potential reduce by 314 B

  • Original 13.9 kB
  • After minification 13.9 kB
  • After compression 13.6 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. Lancers.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

104

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lancers.jp

lancers.jp

362 ms

www.lancers.jp

www.lancers.jp

1051 ms

css2

css2

52 ms

rebranding.min.css

rebranding.min.css

212 ms

faq-modal.min.css

faq-modal.min.css

40 ms

gpt.js

gpt.js

111 ms

react_app_vendors.dll.js

react_app_vendors.dll.js

45 ms

header.js

header.js

49 ms

umd.js

umd.js

5 ms

index.js

index.js

271 ms

appleid.auth.js

appleid.auth.js

236 ms

jquery.cookie.min.js

jquery.cookie.min.js

3 ms

gtm.js

gtm.js

369 ms

OrHui+PogdV6sSr7hMcqoAAAAASUVORK5CYII=

OrHui+PogdV6sSr7hMcqoAAAAASUVORK5CYII=

169 ms

JjNKQkzBzrRjlQ4AfwOvjAErS1jEFgAAAABJRU5ErkJggg==

JjNKQkzBzrRjlQ4AfwOvjAErS1jEFgAAAABJRU5ErkJggg==

163 ms

AAAAAElFTkSuQmCC

AAAAAElFTkSuQmCC

162 ms

477ff250570ad0c610625c0c5b238458-611x382.webp

477ff250570ad0c610625c0c5b238458-611x382.webp

1329 ms

1.webp

1.webp

393 ms

2.webp

2.webp

396 ms

3.webp

3.webp

395 ms

4.webp

4.webp

395 ms

5.webp

5.webp

401 ms

6.webp

6.webp

650 ms

7.webp

7.webp

735 ms

google.svg

google.svg

395 ms

yahoo.png

yahoo.png

399 ms

facebook.svg

facebook.svg

397 ms

apple.svg

apple.svg

398 ms

caret-down.svg

caret-down.svg

734 ms

logo_kddi.png

logo_kddi.png

735 ms

logo_gree.png

logo_gree.png

736 ms

logo_yahoo.png

logo_yahoo.png

731 ms

logo_dentsu.png

logo_dentsu.png

1299 ms

logo_edwin.png

logo_edwin.png

1302 ms

logo_kinkos.png

logo_kinkos.png

1302 ms

logo_persol.png

logo_persol.png

1300 ms

logo_shinsei.png

logo_shinsei.png

1300 ms

mobile.svg

mobile.svg

1298 ms

envelope-open-text.svg

envelope-open-text.svg

1676 ms

bg.webp

bg.webp

1681 ms

img_03.svg

img_03.svg

1681 ms

caret-right.svg

caret-right.svg

1680 ms

img_02.svg

img_02.svg

1684 ms

img_01.svg

img_01.svg

1678 ms

usecase_25.webp

usecase_25.webp

2152 ms

angle-right.svg

angle-right.svg

2132 ms

usecase_5.webp

usecase_5.webp

2150 ms

video_animation_animated_explainer_videos.png

video_animation_animated_explainer_videos.png

2152 ms

usecase_4.webp

usecase_4.webp

2131 ms

online_marketing_social_marketing.png

online_marketing_social_marketing.png

2154 ms

usecase_1.webp

usecase_1.webp

2171 ms

image_2021_6_4-615x432-1-544x382.webp

image_2021_6_4-615x432-1-544x382.webp

1675 ms

retoro1-611x382.webp

retoro1-611x382.webp

1680 ms

usecase_3.webp

usecase_3.webp

2028 ms

logo_lancers.svg

logo_lancers.svg

239 ms

font

font

215 ms

NotoSansCJKjp-DemiLight.woff

NotoSansCJKjp-DemiLight.woff

2076 ms

pubads_impl.js

pubads_impl.js

69 ms

NotoSansCJKjp-Bold.woff

NotoSansCJKjp-Bold.woff

1984 ms

graphics_design_creative_logo_design.png

graphics_design_creative_logo_design.png

1981 ms

payment_invoice.svg

payment_invoice.svg

1939 ms

payment_card.webp

payment_card.webp

1980 ms

img_01.webp

img_01.webp

1980 ms

img_02.webp

img_02.webp

2158 ms

img_03.webp

img_03.webp

2156 ms

img_04.webp

img_04.webp

2156 ms

js

js

281 ms

analytics.js

analytics.js

369 ms

ga.js

ga.js

368 ms

destination

destination

441 ms

destination

destination

510 ms

destination

destination

507 ms

destination

destination

578 ms

bat.js

bat.js

837 ms

s_retargeting.js

s_retargeting.js

1663 ms

conversion.js

conversion.js

1666 ms

a8sales.js

a8sales.js

901 ms

ytag.js

ytag.js

1659 ms

conversion2.js

conversion2.js

1661 ms

fbevents.js

fbevents.js

849 ms

9oio6peuba

9oio6peuba

908 ms

6776814.js

6776814.js

822 ms

pd.js

pd.js

847 ms

kj2578uze0

kj2578uze0

923 ms

js

js

540 ms

img_01.jpg

img_01.jpg

1905 ms

ads

ads

258 ms

container.html

container.html

671 ms

app-store.svg

app-store.svg

1663 ms

google-play-badge.svg

google-play-badge.svg

1647 ms

arrow-up.svg

arrow-up.svg

1644 ms

caret-right.svg

caret-right.svg

1822 ms

xmark.svg

xmark.svg

1802 ms

collect

collect

534 ms

collect

collect

534 ms

collect

collect

519 ms

12337544587260638425

12337544587260638425

650 ms

icon.png

icon.png

657 ms

abg_lite.js

abg_lite.js

1092 ms

window_focus.js

window_focus.js

1125 ms

ufs_web_display.js

ufs_web_display.js

384 ms

5880774433738012890

5880774433738012890

1118 ms

collect

collect

120 ms

analytics

analytics

322 ms

collect

collect

245 ms

collect

collect

243 ms

js

js

456 ms

collect

collect

240 ms

js

js

293 ms

clarity.js

clarity.js

19 ms

ga-audiences

ga-audiences

721 ms

ga-audiences

ga-audiences

528 ms

ga-audiences

ga-audiences

550 ms

ga-audiences

ga-audiences

634 ms

analytics

analytics

632 ms

conversion_async.js

conversion_async.js

1547 ms

js

js

61 ms

td_js_sdk_171.js

td_js_sdk_171.js

210 ms

cv

cv

887 ms

banner.js

banner.js

160 ms

collectedforms.js

collectedforms.js

137 ms

fb.js

fb.js

136 ms

6776814.js

6776814.js

191 ms

uwt.js

uwt.js

20 ms

u

u

428 ms

bean2nsy

bean2nsy

432 ms

adsct

adsct

343 ms

adsct

adsct

250 ms

cv_monitor

cv_monitor

191 ms

bean2nsy

bean2nsy

77 ms

js

js

39 ms

cv_monitor

cv_monitor

9 ms

Accessibility Review

lancers.jp accessibility score

95

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

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

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 doesn't use 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 Lancers.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 Lancers.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

lancers.jp

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