Tools & Wizards About Us
prosheet.jp screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

prosheet.jp

プロシート（PROsheet） | フリーランス向け週２日〜のお仕事紹介。

Page Load Speed

21.6 sec in total

First Response

3.1 sec

Resources Loaded

14.7 sec

Page Rendered

3.7 sec

prosheet.jp screenshot

About Website

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

フリーランスを対象に、業務委託お仕事をご紹介。１日３万円〜、週３で３６万円から。登録から最短１週間で「人力」でご紹介。起業時に、単価UPに。

Visit prosheet.jp

Key Findings

We analyzed Prosheet.jp page load time and found that the first response time was 3.1 sec and then it took 18.4 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

prosheet.jp performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value850 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

prosheet.jp

3140 ms

css

61 ms

texgyreadventor-regular.otf

672 ms

bootstrap.min.css

762 ms

auth.css

590 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 81% of them (79 requests) were addressed to the original Prosheet.jp, 3% (3 requests) were made to Apis.google.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Prosheet.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.4 MB (35%)

Content Size

21.1 MB

After Optimization

13.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 74.2 kB

  • Original 87.2 kB
  • After minification 52.5 kB
  • After compression 13.0 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 34.7 kB, which is 40% 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 74.2 kB or 85% of the original size.

Image Optimization

-34%

Potential reduce by 6.9 MB

  • Original 20.4 MB
  • After minification 13.5 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. Obviously, PROsheet needs image optimization as it can save up to 6.9 MB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 321.1 kB

  • Original 475.8 kB
  • After minification 437.4 kB
  • After compression 154.7 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 321.1 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 112.6 kB

  • Original 135.5 kB
  • After minification 129.7 kB
  • After compression 23.0 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. Prosheet.jp needs all CSS files to be minified and compressed as it can save up to 112.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (20%)

Requests Now

92

After Optimization

74

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prosheet.jp

prosheet.jp

3140 ms

css

css

61 ms

texgyreadventor-regular.otf

texgyreadventor-regular.otf

672 ms

bootstrap.min.css

bootstrap.min.css

762 ms

auth.css

auth.css

590 ms

top.css

top.css

594 ms

common.css

common.css

619 ms

jquery.js

jquery.js

1016 ms

jquery.ui.js

jquery.ui.js

1200 ms

jquery.waypoints.js

jquery.waypoints.js

794 ms

bootstrap.min.js

bootstrap.min.js

839 ms

auth.js

auth.js

871 ms

top.js

top.js

940 ms

conversion.js

conversion.js

42 ms

analytics.js

analytics.js

236 ms

gtm.js

gtm.js

342 ms

sdk.js

sdk.js

491 ms

client:plusone.js

client:plusone.js

294 ms

prosheet_logo.png

prosheet_logo.png

263 ms

ribbon.png

ribbon.png

236 ms

btn-facebook.png

btn-facebook.png

403 ms

btn-google.png

btn-google.png

462 ms

link-to-biz.png

link-to-biz.png

462 ms

link-to-tryout.png

link-to-tryout.png

784 ms

point1.png

point1.png

833 ms

point2.png

point2.png

824 ms

point3.png

point3.png

1149 ms

point4.png

point4.png

1552 ms

arrow-left.png

arrow-left.png

643 ms

arrow-right.png

arrow-right.png

838 ms

anken_01.jpg

anken_01.jpg

1706 ms

anken_04.jpg

anken_04.jpg

1571 ms

anken_03.jpg

anken_03.jpg

2629 ms

anken_02.jpg

anken_02.jpg

1393 ms

anken_05.jpg

anken_05.jpg

1821 ms

anken_06.jpg

anken_06.jpg

2907 ms

step1.png

step1.png

2218 ms

step-arrow.png

step-arrow.png

1774 ms

step2.png

step2.png

2072 ms

step3.png

step3.png

2168 ms

step4.png

step4.png

2439 ms

arrow-left-black.png

arrow-left-black.png

2277 ms

arrow-right-black.png

arrow-right-black.png

2361 ms

face.jpg

face.jpg

3817 ms

face.jpg

face.jpg

2664 ms

face.jpg

face.jpg

2900 ms

face.jpg

face.jpg

2736 ms

face.jpg

face.jpg

4542 ms

welfare-sakura.png

welfare-sakura.png

2867 ms

welfare-cotree.png

welfare-cotree.png

2948 ms

welfare-mrso.jpg

welfare-mrso.jpg

3063 ms

welfare-chatwork.png

welfare-chatwork.png

3107 ms

welfare-anytimes.png

welfare-anytimes.png

3096 ms

welfare-freee.png

welfare-freee.png

3167 ms

65 ms

z2n1Sjxk9souK3HCtdHukgnkfjG14KscmNg0xC38TkM.ttf

z2n1Sjxk9souK3HCtdHukgnkfjG14KscmNg0xC38TkM.ttf

81 ms

collect

collect

38 ms

getOgp

getOgp

6249 ms

collect

collect

206 ms

139 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

122 ms

postmessageRelay

postmessageRelay

58 ms

getOgp

getOgp

5379 ms

futura-webfont.ttf

futura-webfont.ttf

2940 ms

137 ms

xd_arbiter.php

xd_arbiter.php

258 ms

api.js

api.js

47 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

73 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

85 ms

welfare-lightningspot.png

welfare-lightningspot.png

3490 ms

person1.png

person1.png

3603 ms

person2.png

person2.png

3838 ms

person3.png

person3.png

4028 ms

dummy-blog.png

dummy-blog.png

4067 ms

media-techcrunch.jpg

media-techcrunch.jpg

3947 ms

media-askii.png

media-askii.png

3864 ms

media-excite.png

media-excite.png

3784 ms

media-cnet.png

media-cnet.png

4047 ms

media-bridge.png

media-bridge.png

3908 ms

media-asa.png

media-asa.png

4051 ms

media-livedoor.png

media-livedoor.png

4055 ms

media-goo.png

media-goo.png

3956 ms

media-markezine.png

media-markezine.png

4307 ms

media-nifty.png

media-nifty.png

3886 ms

bg-catch.jpg

bg-catch.jpg

3980 ms

logo.png

logo.png

3974 ms

bg-opacity-black.png

bg-opacity-black.png

4037 ms

bg-blue-bar.png

bg-blue-bar.png

3946 ms

bg-persona.png

bg-persona.png

5477 ms

bg-project.png

bg-project.png

4862 ms

bg-project-pop.png

bg-project-pop.png

4029 ms

bg-user-voice.jpg

bg-user-voice.jpg

3937 ms

welfare-title.png

welfare-title.png

4168 ms

bg-recommend.png

bg-recommend.png

6112 ms

bg-media.png

bg-media.png

5174 ms

geekgarage001-150x150.jpg

geekgarage001-150x150.jpg

204 ms

sada001-150x150.jpg

sada001-150x150.jpg

218 ms

Accessibility Review

prosheet.jp accessibility score

52

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

prosheet.jp best practices score

83

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

Page has valid source maps

SEO Factors

prosheet.jp SEO score

86

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

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prosheet.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Prosheet.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

prosheet.jp

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