Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

broedkasse.be

PKnote-PK的吃吃喝喝筆記本

Page Load Speed

3.7 sec in total

First Response

201 ms

Resources Loaded

2.6 sec

Page Rendered

835 ms

About Website

Welcome to broedkasse.be homepage info - get ready to check Broedkasse best content right away, or after learning these important things about broedkasse.be

HI,很高興認識你(///▽///)一個愛吃愛買愛玩愛拍照的水瓶座。喜歡科技、喜歡料理、喜歡旅遊~☆韓國觀光公社自由行宣傳大使Free@Korea 第1~5屆 Korea Messenger☆韓國觀光公社旅遊推廣大使KOREA BUDDIES@TAIPEI 2019 第一屆☆Upaper專欄=來自星星的Korea Me | PKnote-PK的吃吃喝喝筆記本

Visit broedkasse.be

Key Findings

We analyzed Broedkasse.be page load time and found that the first response time was 201 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

broedkasse.be performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value2,640 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.224

56/100

15%

TTI (Time to Interactive)

Value37.9 s

0/100

10%

Network Requests Diagram

broedkasse.be

201 ms

pknote.cc

246 ms

firebase-app.js

31 ms

firebase-messaging.js

40 ms

firebase-script.js

198 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Broedkasse.be, 28% (37 requests) were made to Pknote.cc and 15% (20 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (904 ms) relates to the external source S3-ap-northeast-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 417.4 kB (6%)

Content Size

6.6 MB

After Optimization

6.2 MB

In fact, the total size of Broedkasse.be main page is 6.6 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. Images take 5.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 140.7 kB

  • Original 173.7 kB
  • After minification 170.4 kB
  • After compression 33.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. 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 140.7 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 271.0 kB

  • Original 5.7 MB
  • After minification 5.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. Broedkasse images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.7 kB

  • Original 624.5 kB
  • After minification 624.4 kB
  • After compression 621.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 2.9 kB

  • Original 44.6 kB
  • After minification 44.6 kB
  • After compression 41.7 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. Broedkasse.be has all CSS files already compressed.

Requests Breakdown

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

Requests Now

110

After Optimization

49

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

Accessibility Review

broedkasse.be accessibility score

87

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

broedkasse.be best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

broedkasse.be SEO score

91

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

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Broedkasse.be can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Broedkasse.be 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 description is not detected on the main page of Broedkasse. 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: