Tools & Wizards About Us

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

plug.be

Reclamebureau Plug | Branding, marketing, grafisch ontwerp, verpakkingen, social media, fotografie

Page Load Speed

4.8 sec in total

First Response

363 ms

Resources Loaded

3.9 sec

Page Rendered

470 ms

About Website

Visit plug.be now to see the best up-to-date Plug content and also check out these interesting facts you probably never knew about plug.be

Reclamebureau Plug tilt uw communicatie naar een hoger, professioneel niveau. Vanuit hun homebase in Roeselare neemt het creatieve team van Bert Bartsoen…

Visit plug.be

Key Findings

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

Performance Metrics

plug.be performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

plug.be

363 ms

plug.be

378 ms

www.plug.be

272 ms

www.plug.be

1768 ms

imw1xxc.css

91 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 63% of them (31 requests) were addressed to the original Plug.be, 8% (4 requests) were made to Use.typekit.net and 6% (3 requests) 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 Plug.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 408.3 kB (13%)

Content Size

3.1 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Plug.be main page is 3.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. 70% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 51.8 kB

  • Original 60.4 kB
  • After minification 60.3 kB
  • After compression 8.6 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 51.8 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 13.3 kB

  • Original 2.5 MB
  • After minification 2.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. Plug images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 226.0 kB

  • Original 375.5 kB
  • After minification 375.5 kB
  • After compression 149.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 226.0 kB or 60% of the original size.

CSS Optimization

-89%

Potential reduce by 117.2 kB

  • Original 131.8 kB
  • After minification 103.8 kB
  • After compression 14.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. Plug.be needs all CSS files to be minified and compressed as it can save up to 117.2 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (39%)

Requests Now

41

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

plug.be accessibility score

71

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

Links do not have a discernible name

Best Practices

plug.be best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

plug.be SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plug.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch 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 Plug.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 data is detected on the main page of Plug. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: