Foodbank-Liege.Be - Info foodbank-liege.be

foodbank-liege.be receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank foodbank-liege.be is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in France and links to network IP address 213.186.33.19. This server supports HTTPS and HTTP/2.

About - foodbank-liege.be


Technologies used on Website

Web Servers
Apache
Programming Languages
PHP

foodbank-liege.be Profile

Last update was 212 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with foodbank-liege.be in any way. Only publicly available statistics data are displayed.

How popular is foodbank-liege.be?

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Unique Visitors:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
0%
Referral:
0%
Search:
0%
Social:
0%
Paid:
0%

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  foodbank-liege.be
Rank:
(Rank based on keywords, cost and organic traffic)
  35,156,904
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  3
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is foodbank-liege.be?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
foodbank-liege.be
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
foodbank-liege.be
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much foodbank-liege.be can earn?

Daily Revenue:
n/a
Monthly Revenue:
n/a
Yearly Revenue:
n/a
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do foodbank-liege.be lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is foodbank-liege.be worth?

Website Value:
n/a

+ Where is foodbank-liege.be hosted?

Server IP:
213.186.33.19
ASN:
AS16276 
ISP:
OVH SAS 
Server Location:

France, FR
 

Other sites hosted on 213.186.33.19

+ How fast does foodbank-liege.be load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 217 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
217
Maximum DOM Depth
12
Maximum Child Elements
54
Minify JavaScript - Potential savings of 39 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
https://www.foodbank-liege.be/js/jquery-3.3.1.js
79 KB39 KB
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://foodbank-liege.be/)
0
https://www.foodbank-liege.be/
190
Keep request counts low and transfer sizes small - 15 requests • 570 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
15570 KB
Image
11484 KB
Script
179 KB
Document
15 KB
Stylesheet
12 KB
Other
10 KB
Media
00 KB
Font
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 250 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://www.foodbank-liege.be/css/style.css
2 KB70
https://www.foodbank-liege.be/js/jquery-3.3.1.js
79 KB150
Efficiently encode images - Potential savings of 100 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
https://www.foodbank-liege.be/images/CamionBAL.jpg
232 KB100 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://foodbank-liege.be/
0 ms109 ms0 KB0 KB302text/html
https://www.foodbank-liege.be/
109 ms239 ms5 KB16 KB200text/htmlDocument
https://www.foodbank-liege.be/css/style.css
253 ms354 ms2 KB9 KB200text/cssStylesheet
https://www.foodbank-liege.be/js/jquery-3.3.1.js
253 ms372 ms79 KB265 KB200application/javascriptScript
https://www.foodbank-liege.be/images/logo.png
254 ms370 ms68 KB68 KB200image/pngImage
https://www.foodbank-liege.be/images/fb_logo.png
254 ms354 ms12 KB12 KB200image/pngImage
https://www.foodbank-liege.be/images/CamionBAL.jpg
355 ms745 ms233 KB232 KB200image/jpegImage
https://www.foodbank-liege.be/images/separator.png
372 ms475 ms1 KB0 KB200image/pngImage
https://www.foodbank-liege.be/images/blason.jpg
414 ms515 ms37 KB37 KB200image/jpegImage
https://www.foodbank-liege.be/images/Schema_Distribution.png
414 ms609 ms124 KB124 KB200image/pngImage
https://www.foodbank-liege.be/images/gratuit.png
414 ms514 ms2 KB2 KB200image/pngImage
https://www.foodbank-liege.be/images/qualite.png
414 ms514 ms2 KB1 KB200image/pngImage
https://www.foodbank-liege.be/images/distribution.png
415 ms574 ms2 KB2 KB200image/pngImage
https://www.foodbank-liege.be/images/benevolat.png
415 ms616 ms2 KB2 KB200image/pngImage
https://www.foodbank-liege.be/images/toppage.png
415 ms615 ms1 KB1 KB200image/pngImage
Serve static assets with an efficient cache policy - 13 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://www.foodbank-liege.be/images/CamionBAL.jpg
900000 ms233 KB
https://www.foodbank-liege.be/images/Schema_Distribution.png
900000 ms124 KB
https://www.foodbank-liege.be/js/jquery-3.3.1.js
900000 ms79 KB
https://www.foodbank-liege.be/images/logo.png
900000 ms68 KB
https://www.foodbank-liege.be/images/blason.jpg
900000 ms37 KB
https://www.foodbank-liege.be/images/fb_logo.png
900000 ms12 KB
https://www.foodbank-liege.be/images/benevolat.png
900000 ms2 KB
https://www.foodbank-liege.be/images/gratuit.png
900000 ms2 KB
https://www.foodbank-liege.be/css/style.css
900000 ms2 KB
https://www.foodbank-liege.be/images/distribution.png
900000 ms2 KB
https://www.foodbank-liege.be/images/qualite.png
900000 ms2 KB
https://www.foodbank-liege.be/images/toppage.png
900000 ms1 KB
https://www.foodbank-liege.be/images/separator.png
900000 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
265 ms
9 ms
407 ms
33 ms
440 ms
55 ms
503 ms
22 ms
646 ms
7 ms
772 ms
6 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
139 ms4 ms1 ms
Properly size images - Potential savings of 193 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
https://www.foodbank-liege.be/images/Schema_Distribution.png
124 KB79 KB
https://www.foodbank-liege.be/images/logo.png
68 KB67 KB
https://www.foodbank-liege.be/images/blason.jpg
37 KB35 KB
https://www.foodbank-liege.be/images/fb_logo.png
12 KB11 KB
Avoids enormous network payloads - Total size was 570 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.foodbank-liege.be/images/CamionBAL.jpg
233 KB
https://www.foodbank-liege.be/images/Schema_Distribution.png
124 KB
https://www.foodbank-liege.be/js/jquery-3.3.1.js
79 KB
https://www.foodbank-liege.be/images/logo.png
68 KB
https://www.foodbank-liege.be/images/blason.jpg
37 KB
https://www.foodbank-liege.be/images/fb_logo.png
12 KB
https://www.foodbank-liege.be/
5 KB
https://www.foodbank-liege.be/images/benevolat.png
2 KB
https://www.foodbank-liege.be/images/gratuit.png
2 KB
https://www.foodbank-liege.be/css/style.css
2 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
51 ms
Rendering
41 ms
Other
35 ms
Script Evaluation
29 ms
Parse HTML & CSS
8 ms
Script Parsing & Compilation
7 ms
Serve images in next-gen formats - Potential savings of 278 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://www.foodbank-liege.be/images/CamionBAL.jpg
232 KB157 KB
https://www.foodbank-liege.be/images/Schema_Distribution.png
124 KB98 KB
https://www.foodbank-liege.be/images/logo.png
68 KB14 KB
https://www.foodbank-liege.be/images/fb_logo.png
12 KB10 KB
Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 130 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Minimize Critical Requests Depth - 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

96
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Meaningful Paint 2.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
First Contentful Paint (3G) 4428 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 15 requests • 570 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
15570 KB
Image
11484 KB
Script
179 KB
Document
15 KB
Stylesheet
12 KB
Other
10 KB
Media
00 KB
Font
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 920 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://www.foodbank-liege.be/css/style.css
2 KB180
https://www.foodbank-liege.be/js/jquery-3.3.1.js
79 KB630
Efficiently encode images - Potential savings of 100 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
https://www.foodbank-liege.be/images/CamionBAL.jpg
232 KB100 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://foodbank-liege.be/
0 ms303 ms0 KB0 KB302text/html
https://www.foodbank-liege.be/
304 ms547 ms5 KB16 KB200text/htmlDocument
https://www.foodbank-liege.be/css/style.css
561 ms661 ms2 KB9 KB200text/cssStylesheet
https://www.foodbank-liege.be/js/jquery-3.3.1.js
561 ms779 ms79 KB265 KB200application/javascriptScript
https://www.foodbank-liege.be/images/logo.png
562 ms942 ms68 KB68 KB200image/pngImage
https://www.foodbank-liege.be/images/fb_logo.png
562 ms850 ms12 KB12 KB200image/pngImage
https://www.foodbank-liege.be/images/CamionBAL.jpg
812 ms1011 ms233 KB232 KB200image/jpegImage
https://www.foodbank-liege.be/images/separator.png
813 ms913 ms1 KB0 KB200image/pngImage
https://www.foodbank-liege.be/images/blason.jpg
813 ms1007 ms37 KB37 KB200image/jpegImage
https://www.foodbank-liege.be/images/Schema_Distribution.png
813 ms1267 ms124 KB124 KB200image/pngImage
https://www.foodbank-liege.be/images/gratuit.png
813 ms948 ms2 KB2 KB200image/pngImage
https://www.foodbank-liege.be/images/qualite.png
813 ms1016 ms2 KB1 KB200image/pngImage
https://www.foodbank-liege.be/images/distribution.png
813 ms1039 ms2 KB2 KB200image/pngImage
https://www.foodbank-liege.be/images/benevolat.png
813 ms1046 ms2 KB2 KB200image/pngImage
https://www.foodbank-liege.be/images/toppage.png
814 ms1104 ms1 KB1 KB200image/pngImage
Serve static assets with an efficient cache policy - 13 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://www.foodbank-liege.be/images/CamionBAL.jpg
900000 ms233 KB
https://www.foodbank-liege.be/images/Schema_Distribution.png
900000 ms124 KB
https://www.foodbank-liege.be/js/jquery-3.3.1.js
900000 ms79 KB
https://www.foodbank-liege.be/images/logo.png
900000 ms68 KB
https://www.foodbank-liege.be/images/blason.jpg
900000 ms37 KB
https://www.foodbank-liege.be/images/fb_logo.png
900000 ms12 KB
https://www.foodbank-liege.be/images/benevolat.png
900000 ms2 KB
https://www.foodbank-liege.be/images/gratuit.png
900000 ms2 KB
https://www.foodbank-liege.be/css/style.css
900000 ms2 KB
https://www.foodbank-liege.be/images/distribution.png
900000 ms2 KB
https://www.foodbank-liege.be/images/qualite.png
900000 ms2 KB
https://www.foodbank-liege.be/images/toppage.png
900000 ms1 KB
https://www.foodbank-liege.be/images/separator.png
900000 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
568 ms
8 ms
806 ms
27 ms
833 ms
62 ms
899 ms
7 ms
1046 ms
6 ms
1063 ms
16 ms
1082 ms
5 ms
JavaScript execution time - 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
575 ms12 ms4 ms
https://www.foodbank-liege.be/js/jquery-3.3.1.js
95 ms70 ms22 ms
Properly size images - Potential savings of 100 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
https://www.foodbank-liege.be/images/logo.png
68 KB65 KB
https://www.foodbank-liege.be/images/blason.jpg
37 KB27 KB
https://www.foodbank-liege.be/images/fb_logo.png
12 KB9 KB
Avoids enormous network payloads - Total size was 570 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.foodbank-liege.be/images/CamionBAL.jpg
233 KB
https://www.foodbank-liege.be/images/Schema_Distribution.png
124 KB
https://www.foodbank-liege.be/js/jquery-3.3.1.js
79 KB
https://www.foodbank-liege.be/images/logo.png
68 KB
https://www.foodbank-liege.be/images/blason.jpg
37 KB
https://www.foodbank-liege.be/images/fb_logo.png
12 KB
https://www.foodbank-liege.be/
5 KB
https://www.foodbank-liege.be/images/benevolat.png
2 KB
https://www.foodbank-liege.be/images/gratuit.png
2 KB
https://www.foodbank-liege.be/css/style.css
2 KB
Minimizes main-thread work - 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
268 ms
Rendering
137 ms
Other
130 ms
Script Evaluation
87 ms
Script Parsing & Compilation
27 ms
Parse HTML & CSS
26 ms
Serve images in next-gen formats - Potential savings of 278 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://www.foodbank-liege.be/images/CamionBAL.jpg
232 KB157 KB
https://www.foodbank-liege.be/images/Schema_Distribution.png
124 KB98 KB
https://www.foodbank-liege.be/images/logo.png
68 KB14 KB
https://www.foodbank-liege.be/images/fb_logo.png
12 KB10 KB
Avoids an excessive DOM size - 217 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
217
Maximum DOM Depth
12
Maximum Child Elements
54
Minify JavaScript - Potential savings of 39 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
https://www.foodbank-liege.be/js/jquery-3.3.1.js
79 KB39 KB
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://foodbank-liege.be/)
0
https://www.foodbank-liege.be/
630
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 240 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Minimize Critical Requests Depth - 2 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

https://www.foodbank-liege.be/js/jquery-3.3.1.js
Optimize CSS Delivery of the following:

https://www.foodbank-liege.be/css/style.css

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Que faisons-nous and 2 others render only 7 pixels tall (18 CSS pixels) .
Associations and 2 others render only 7 pixels tall (18 CSS pixels) .
Tous les surpl…titre gratuit. and 20 others render only 7 pixels tall (18 CSS pixels) .
Déclaration un…its de l&#39;Homme and 2 others render only 7 pixels tall (18 CSS pixels) .
Toute personne…ux nécessaires and 1 others render only 7 pixels tall (18 CSS pixels) .
les surplus renders only 7 pixels tall (18 CSS pixels).
elle contrôle…de péremption, and 3 others render only 7 pixels tall (18 CSS pixels).
« Vous ne donn…réellement » renders only 7 pixels tall (18 CSS pixels).
(Khalil Gibran) renders only 7 pixels tall (18 CSS pixels).
Président - Re…ions publiques and 18 others render only 7 pixels tall (18 CSS pixels).
president@bal-asbl.be renders only 7 pixels tall (18 CSS pixels).
Informatique,…lic &amp; intranet and 28 others render only 7 pixels tall (18 CSS pixels).
Copyright © 20…oits réservés. renders only 7 pixels tall (18 CSS pixels).
En continuant…ation. Voir la and 1 others render only 7 pixels tall (18 CSS pixels) .
politique de confidentialité renders only 7 pixels tall (18 CSS pixels) .
J&#39;ACCEPTE renders only 7 pixels tall (18 CSS pixels) .

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 204.6KiB (66% reduction).

Compressing https://www.foodbank-liege.be/images/CamionBAL.jpg could save 138.8KiB (59% reduction).
Compressing and resizing https://www.foodbank-liege.be/images/logo.png could save 63.3KiB (93% reduction).
Compressing https://www.foodbank-liege.be/images/benevolat.png could save 778B (36% reduction).
Compressing https://www.foodbank-liege.be/images/gratuit.png could save 631B (37% reduction).
Compressing https://www.foodbank-liege.be/images/distribution.png could save 542B (35% reduction).
Compressing https://www.foodbank-liege.be/images/toppage.png could save 362B (53% reduction).
Compressing https://www.foodbank-liege.be/images/qualite.png could save 240B (19% reduction).

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.foodbank-liege.be/css/style.css (15 minutes)
https://www.foodbank-liege.be/images/CamionBAL.jpg (15 minutes)
https://www.foodbank-liege.be/images/Schema_Distribution.png (15 minutes)
https://www.foodbank-liege.be/images/benevolat.png (15 minutes)
https://www.foodbank-liege.be/images/blason.jpg (15 minutes)
https://www.foodbank-liege.be/images/distribution.png (15 minutes)
https://www.foodbank-liege.be/images/fb_logo.png (15 minutes)
https://www.foodbank-liege.be/images/gratuit.png (15 minutes)
https://www.foodbank-liege.be/images/logo.png (15 minutes)
https://www.foodbank-liege.be/images/qualite.png (15 minutes)
https://www.foodbank-liege.be/images/separator.png (15 minutes)
https://www.foodbank-liege.be/images/toppage.png (15 minutes)
https://www.foodbank-liege.be/js/jquery-3.3.1.js (15 minutes)

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 40.3KiB (51% reduction).

Minifying https://www.foodbank-liege.be/js/jquery-3.3.1.js could save 40.3KiB (51% reduction) after compression.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/quefaisonsnous">Que faisons-nous</a> is close to 1 other tap targets .

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 189B (12% reduction).

Minifying https://www.foodbank-liege.be/css/style.css could save 189B (12% reduction) after compression.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does foodbank-liege.be use compression?

foodbank-liege.be use gzip compression.
Original size: 15.98 KB
Compressed size: 4.29 KB
File reduced by: 11.69 KB (73%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

foodbank-liege.be supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: foodbank-liege.be
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Aug 23 22:51:40 2019 GMT
Valid until: Nov 21 22:51:40 2019 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

foodbank-liege.be supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Fri, 06 Sep 2019 09:18:46 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 213
Server: Apache
Location: https://www.foodbank-liege.be
Set-Cookie: SERVERID108286=102118|XXIke|XXIke; path=/
X-IPLB-Instance: 30850

HTTP/2 200 
date: Fri, 06 Sep 2019 09:18:46 GMT
content-type: text/html; charset=UTF-8
server: Apache
x-powered-by: PHP/7.1
cache-control: max-age=0, must-revalidate, private
vary: Accept-Encoding
content-encoding: gzip
x-iplb-instance: 30837
set-cookie: SERVERID108286=102118|XXIke|XXIke; path=/

+ DNS Lookup

Type Ip Target TTL
TXT 600
A 213.186.33.19 3600
MX mx2.ovh.net 3600
MX mx1.ovh.net 3600
SOA 3600
Mname dns12.ovh.net
Rname tech.ovh.net
Serial Number 2019052406
Refresh 86400
Retry 3600
Expire 3600000
Minimum TTL 0
NS ns12.ovh.net 3600
NS dns12.ovh.net 3600

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.dns.be...
% .be Whois Server 6.1
%
% The WHOIS service offered by DNS Belgium and the access to the records in the DNS Belgium
% WHOIS database are provided for information purposes only. It allows
% persons to check whether a specific domain name is still available or not
% and to obtain information related to the registration records of
% existing domain names.
%
% DNS Belgium cannot, under any cir***stances, be held liable where the stored
% information would prove to be incomplete or inaccurate in any sense.
%
% By submitting a query you agree not to use the information made available
% to:
% - allow, enable or otherwise support the transmission of unsolicited,
% commercial advertising or other solicitations whether via email or otherwise;
% - target advertising in any possible way;
% - to cause nuisance in any possible way to the domain name holders by sending
% messages to them (whether by automated, electronic processes capable of
% enabling high volumes or other possible means).
%
% Without prejudice to the above, it is explicitly forbidden to extract, copy
% and/or use or re-utilise in any form and by any means (electronically or
% not) the whole or a quantitatively or qualitatively substantial part
% of the contents of the WHOIS database without prior and explicit permission
% by DNS Belgium, nor in any attempt thereof, to apply automated, electronic
% processes to DNS Belgium (or its systems).
%
% You agree that any reproduction and/or transmission of data for commercial
% purposes will always be considered as the extraction of a substantial
% part of the content of the WHOIS database.
%
% By submitting the query you agree to abide by this policy and accept that
% DNS Belgium can take measures to limit the use of its whois services in order to
% protect the privacy of its registrants or the integrity of the database.
%

Domain: foodbank-liege.be
Status: NOT AVAILABLE
Registered: Tue Apr 1 2008

Registrant:
Not shown, please visit www.dnsbelgium.be for webbased whois.

Registrar Technical Contacts:

Registrar:
Name: OVH
Website: http://www.ovh.com

Nameservers:
ns12.ovh.net
dns12.ovh.net

Keys:

Flags:
clientTransferProhibited

Please visit www.dnsbelgium.be for more info.
Last update was 212 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with foodbank-liege.be in any way. Only publicly available statistics data are displayed.
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
foodbank-liege.be widget