Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

plein.fi

RESTAURANT PLEIN - natural wines & excellent food in vallila

Page Load Speed

7.8 sec in total

First Response

1.8 sec

Resources Loaded

5.7 sec

Page Rendered

394 ms

plein.fi screenshot

About Website

Click here to check amazing PLEIN content. Otherwise, check out these important facts you probably never knew about plein.fi

natural wines & excellent food in vallila, helsinki. serving authentic flavours made from scratch

Visit plein.fi

Key Findings

We analyzed Plein.fi page load time and found that the first response time was 1.8 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

plein.fi performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

www.plein.fi

1762 ms

style.min.css

142 ms

font-libre-franklin.css

281 ms

style.css

469 ms

blocks.css

358 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 97% of them (29 requests) were addressed to the original Plein.fi, 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Plein.fi.

Page Optimization Overview & Recommendations

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

Content Size

1.0 MB

After Optimization

913.5 kB

In fact, the total size of Plein.fi main page is 1.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. 40% of websites need less resources to load. Images take 817.8 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 79.0 kB

  • Original 108.4 kB
  • After minification 107.1 kB
  • After compression 29.3 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 79.0 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 11.4 kB

  • Original 817.8 kB
  • After minification 806.4 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. PLEIN images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 9.3 kB

  • Original 55.8 kB
  • After minification 55.8 kB
  • After compression 46.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 9.3 kB or 17% of the original size.

CSS Optimization

-33%

Potential reduce by 15.3 kB

  • Original 46.7 kB
  • After minification 46.7 kB
  • After compression 31.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. Plein.fi needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (57%)

Requests Now

21

After Optimization

9

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

Accessibility Review

plein.fi accessibility score

98

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.

Best Practices

plein.fi 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

plein.fi SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plein.fi can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Plein.fi 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 PLEIN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: