Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

flpark.net

フリーランサーズ パーク ~ご近所のフリーランス同士を結ぶ、仲間探しサービス~

Page Load Speed

4.7 sec in total

First Response

587 ms

Resources Loaded

3.9 sec

Page Rendered

162 ms

flpark.net screenshot

About Website

Click here to check amazing Flpark content. Otherwise, check out these important facts you probably never knew about flpark.net

「フリーランサーズ パーク」は、様々なデータでフリーランス同士を結ぶ、フリーランスのための仲間探しサービスです

Visit flpark.net

Key Findings

We analyzed Flpark.net page load time and found that the first response time was 587 ms and then it took 4.1 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

flpark.net performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

flpark.net

587 ms

www.flpark.net

809 ms

reset-min.css

7 ms

index.css

541 ms

jquery.min.js

33 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 33% of them (15 requests) were addressed to the original Flpark.net, 17% (8 requests) were made to Apis.google.com and 7% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Flpark.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.0 kB (11%)

Content Size

531.9 kB

After Optimization

472.9 kB

In fact, the total size of Flpark.net main page is 531.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. 35% of websites need less resources to load. Images take 437.4 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 13.0 kB

  • Original 19.4 kB
  • After minification 19.3 kB
  • After compression 6.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. 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 13.0 kB or 67% of the original size.

Image Optimization

-1%

Potential reduce by 2.8 kB

  • Original 437.4 kB
  • After minification 434.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. Flpark images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 30.4 kB

  • Original 58.7 kB
  • After minification 49.2 kB
  • After compression 28.3 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 30.4 kB or 52% of the original size.

CSS Optimization

-79%

Potential reduce by 12.9 kB

  • Original 16.4 kB
  • After minification 12.4 kB
  • After compression 3.5 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. Flpark.net needs all CSS files to be minified and compressed as it can save up to 12.9 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

23

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

Accessibility Review

flpark.net accessibility score

83

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-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

Best Practices

flpark.net 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

flpark.net SEO score

98

Search Engine Optimization Advices

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 Flpark.net 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 Flpark.net 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

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