2.1 sec in total
293 ms
1.6 sec
195 ms
Visit offscreen.be now to see the best up-to-date Offscreen content and also check out these interesting facts you probably never knew about offscreen.be
Offscreen: join the cult !
Visit offscreen.beWe analyzed Offscreen.be page load time and found that the first response time was 293 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
offscreen.be performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value5.0 s
27/100
25%
Value3.9 s
83/100
10%
Value160 ms
94/100
30%
Value0.08
94/100
15%
Value5.3 s
73/100
10%
293 ms
262 ms
181 ms
304 ms
331 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 72% of them (48 requests) were addressed to the original Offscreen.be, 12% (8 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (998 ms) belongs to the original domain Offscreen.be.
Page size can be reduced by 631.2 kB (51%)
1.2 MB
611.9 kB
In fact, the total size of Offscreen.be main page is 1.2 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. 65% of websites need less resources to load. Images take 483.4 kB which makes up the majority of the site volume.
Potential reduce by 70.7 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 70.7 kB or 91% of the original size.
Potential reduce by 46.5 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. Offscreen images are well optimized though.
Potential reduce by 190.0 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 190.0 kB or 64% of the original size.
Potential reduce by 324.1 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. Offscreen.be needs all CSS files to be minified and compressed as it can save up to 324.1 kB or 84% of the original size.
Number of requests can be reduced by 27 (48%)
56
29
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Offscreen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
offscreen.be
293 ms
www.offscreen.be
262 ms
system.base.css
181 ms
calendar_multiday.css
304 ms
date.css
331 ms
datepicker.1.7.css
333 ms
node.css
334 ms
lazyloader.css
338 ms
ctools.css
337 ms
panels.css
336 ms
statik-two-col-right.css
408 ms
date_views.css
410 ms
onecol.css
418 ms
locale.css
419 ms
main.css
506 ms
jquery.min.js
7 ms
jquery.once.js
484 ms
drupal.js
485 ms
jquery.lazyloader.js
487 ms
googleanalytics.js
499 ms
admin_menu.js
497 ms
modernizr.custom.min.js
573 ms
plugins.js
574 ms
main.js
579 ms
logo.png
679 ms
offscreen_website_banner_2016_825.jpg
998 ms
wtmLKrxR6H0.jpg
750 ms
presale_tickets.jpg
927 ms
001.jpg
658 ms
002.jpg
659 ms
003.jpg
726 ms
004.jpg
735 ms
005.jpg
747 ms
logo_pure_fm1.png
807 ms
cocof_logo_2016.jpg
818 ms
motel_one_logo.jpg
832 ms
ritcs_logo_2016.jpg
833 ms
logo_bozar_cinema.png
887 ms
wtmLKrxR6H0
98 ms
www-embed-player-vflfNyN_r.css
37 ms
www-embed-player.js
55 ms
base.js
80 ms
agenda.jpg
732 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
38 ms
ad_status.js
41 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
37 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
39 ms
tv_brussel_logo1.jpg
624 ms
partners_fed_wal_bxl.jpg
599 ms
vaf_logo_2016.jpg
647 ms
acht_tv_logo.jpg
661 ms
fm_brussel_logo.jpg
674 ms
brussels_hoofdstedelijk_gewest.jpg
676 ms
logo_stad_brussel.png
680 ms
partners_cinematek_1.jpg
650 ms
nova_black.jpg
666 ms
vgc_logo_2016.jpg
679 ms
css
26 ms
ga.js
53 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
36 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
36 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
36 ms
-91TwiFzqeL1F7Kh91APwYnF5uFdDttMLvmWuJdhhgs.ttf
36 ms
uDssvmXgp7Nj3i336k_dSonF5uFdDttMLvmWuJdhhgs.ttf
35 ms
MG9KbUZFchDs94Tbv9U-paCWcynf_cDxXwCLxiixG1c.ttf
36 ms
AAAAEAAAAAAAEAAABAAAAAAAAAAAAAAAAAAAADAAAAAACAAAABAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABAAANAQAADQEAADABAAAwAAAAAAACgBeAJABBAFqAqIDEgMwA1ADXgOaAAAAAQAAAAwA0wAKAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAA4ArgABAAAAAAABAB4AAAABAAAAAAACAA4AfwABAAAAAAADAB4ANAABAAAAAAAEAB4AjQABAAAAAAAFABYAHgABAAAAAAAGAA8AUgABAAAAAAAKACgAqwADAAEECQABAB4AAAADAAEECQACAA4AfwADAAEECQADAB4ANAADAAEECQAEAB4AjQADAAEECQAFABYAHgADAAEECQAGAB4AYQADAAEECQAKACgAqwBvAGYAZgBzAGMAcgBlAGUAbgAtAGcAbAB5AHAAaABWAGUAcgBzAGkAbwBuACAAMAAuADAAbwBmAGYAcwBjAHIAZQBlAG4ALQBnAGwAeQBwAGhvZmZzY3JlZW4tZ2x5cGgAbwBmAGYAcwBjAHIAZQBlAG4ALQBnAGwAeQBwAGgAUgBlAGcAdQBsAGEAcgBvAGYAZgBzAGMAcgBlAGUAbgAtAGcAbAB5AHAAaABHAGUAbgBlAHIAYQB0AGUAZAAgAGIAeQAgAEkAYwBvAE0AbwBvAG4AAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
4 ms
__utm.gif
26 ms
offscreen.be accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
offscreen.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
offscreen.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Offscreen.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Offscreen.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.
offscreen.be
Open Graph description is not detected on the main page of Offscreen. 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: