Tools & Wizards About Us
phare.irisnet.be screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

phare.irisnet.be

Accueil - Service PHARE

Page Load Speed

2.5 sec in total

First Response

795 ms

Resources Loaded

1.6 sec

Page Rendered

103 ms

phare.irisnet.be screenshot

About Website

Click here to check amazing PHARE Irisnet content for Belgium. Otherwise, check out these important facts you probably never knew about phare.irisnet.be

PHARE - Personne Handicapée Autonomie Recherché.

Visit phare.irisnet.be

Key Findings

We analyzed Phare.irisnet.be page load time and found that the first response time was 795 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

phare.irisnet.be performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

phare.irisnet.be

795 ms

main.css

75 ms

layout.css

506 ms

font.css

74 ms

web.js.c6c03a41ab43c1a3c416.js

334 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Phare.irisnet.be, 46% (19 requests) were made to U.jimdo.com and 15% (6 requests) were made to Image.jimcdn.com. The less responsive or slowest element that took the longest time to load (795 ms) belongs to the original domain Phare.irisnet.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 752.1 kB (59%)

Content Size

1.3 MB

After Optimization

516.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phare.irisnet.be main page is 1.3 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. 75% 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. Javascripts take 800.7 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 42.7 kB

  • Original 61.1 kB
  • After minification 50.2 kB
  • After compression 18.4 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. This page needs HTML code to be minified as it can gain 11.0 kB, which is 18% 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 42.7 kB or 70% of the original size.

Image Optimization

-20%

Potential reduce by 34.7 kB

  • Original 169.9 kB
  • After minification 135.2 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. Obviously, PHARE Irisnet needs image optimization as it can save up to 34.7 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 504.1 kB

  • Original 800.7 kB
  • After minification 800.7 kB
  • After compression 296.6 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 504.1 kB or 63% of the original size.

CSS Optimization

-72%

Potential reduce by 170.6 kB

  • Original 236.5 kB
  • After minification 235.6 kB
  • After compression 65.9 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. Phare.irisnet.be needs all CSS files to be minified and compressed as it can save up to 170.6 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (56%)

Requests Now

39

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PHARE Irisnet. 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.

Network Requests Diagram

phare.irisnet.be

phare.irisnet.be

795 ms

main.css

main.css

75 ms

layout.css

layout.css

506 ms

font.css

font.css

74 ms

web.js.c6c03a41ab43c1a3c416.js

web.js.c6c03a41ab43c1a3c416.js

334 ms

jquery-1-9-0-min.js

jquery-1-9-0-min.js

697 ms

css

css

37 ms

web_oldtemplate.css.f5b74ba49d36b45eadb9ea71f01563b1.css

web_oldtemplate.css.f5b74ba49d36b45eadb9ea71f01563b1.css

77 ms

image.gif

image.gif

166 ms

cocof-icone.png

cocof-icone.png

17 ms

logo-phare-baseline.png

logo-phare-baseline.png

50 ms

sourds-header.png

sourds-header.png

50 ms

facile-a-lire-header.png

facile-a-lire-header.png

50 ms

illustration.png

illustration.png

76 ms

image.gif

image.gif

165 ms

image.gif

image.gif

160 ms

image.gif

image.gif

143 ms

image.gif

image.gif

161 ms

logo-du-service-phare.png

logo-du-service-phare.png

140 ms

ariane.png

ariane.png

71 ms

oeil-icone.png

oeil-icone.png

64 ms

arrows-mini-menu.svg

arrows-mini-menu.svg

62 ms

print.gif

print.gif

70 ms

une-bg.jpg

une-bg.jpg

86 ms

st.js

st.js

64 ms

box-resume-bg.png

box-resume-bg.png

71 ms

totop.png

totop.png

67 ms

top-bg.png

top-bg.png

253 ms

websites-icon.png

websites-icon.png

70 ms

ga.js

ga.js

63 ms

analytics.js

analytics.js

113 ms

loginstate

loginstate

258 ms

info.png

info.png

52 ms

widget.js

widget.js

102 ms

__utm.gif

__utm.gif

27 ms

__utm.gif

__utm.gif

38 ms

__utm.gif

__utm.gif

40 ms

collect

collect

18 ms

swiftype_nocode-bcc8d1c39f18a7802a7ee2c6f76577f3.css

swiftype_nocode-bcc8d1c39f18a7802a7ee2c6f76577f3.css

13 ms

swiftype_nocode-d8273559be65c04593eb2a85dc0df637.js

swiftype_nocode-d8273559be65c04593eb2a85dc0df637.js

27 ms

embed_mag-115e233edebef5dbcde4c557157b625c.png

embed_mag-115e233edebef5dbcde4c557157b625c.png

8 ms

Accessibility Review

phare.irisnet.be accessibility score

74

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

Links do not have a discernible name

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

phare.irisnet.be best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

phare.irisnet.be SEO score

96

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phare.irisnet.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Phare.irisnet.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

phare.irisnet.be

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