Tools & Wizards About Us
dev.inbound.be screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

dev.inbound.be

Inbound. Users

Page Load Speed

3.6 sec in total

First Response

533 ms

Resources Loaded

2.9 sec

Page Rendered

168 ms

dev.inbound.be screenshot

About Website

Visit dev.inbound.be now to see the best up-to-date Dev Inbound content for Belgium and also check out these interesting facts you probably never knew about dev.inbound.be

Visit dev.inbound.be

Key Findings

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

Performance Metrics

dev.inbound.be performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

login

533 ms

bootstrap.min.css

1133 ms

font-awesome.min.css

1090 ms

login.css

156 ms

css

147 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 20% of them (2 requests) were addressed to the original Dev.inbound.be, 40% (4 requests) were made to Fonts.gstatic.com and 30% (3 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Maxcdn.bootstrapcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.9 kB (82%)

Content Size

135.4 kB

After Optimization

24.5 kB

  • HTML
  • CSS

In fact, the total size of Dev.inbound.be main page is 135.4 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. 20% of websites need less resources to load. CSS take 132.9 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 1.6 kB

  • Original 2.4 kB
  • After minification 2.2 kB
  • After compression 872 B

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 270 B, which is 11% 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 1.6 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 109.3 kB

  • Original 132.9 kB
  • After minification 132.3 kB
  • After compression 23.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. Dev.inbound.be needs all CSS files to be minified and compressed as it can save up to 109.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (75%)

Requests Now

4

After Optimization

1

  • CSS

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

Network Requests Diagram

login

login

533 ms

bootstrap.min.css

bootstrap.min.css

1133 ms

font-awesome.min.css

font-awesome.min.css

1090 ms

login.css

login.css

156 ms

css

css

147 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

143 ms

zJY4gsxBiSo5L7tNutxFNg.ttf

zJY4gsxBiSo5L7tNutxFNg.ttf

213 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

252 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

255 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

150 ms

Accessibility Review

dev.inbound.be accessibility score

81

Accessibility Issues

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

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

dev.inbound.be best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dev.inbound.be SEO score

88

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dev.inbound.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Dev.inbound.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

dev.inbound.be

Open Graph description is not detected on the main page of Dev Inbound. 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: