3.1 sec in total
444 ms
2.4 sec
188 ms
Click here to check amazing 20 Something content. Otherwise, check out these important facts you probably never knew about 20something.be
Visit 20something.beWe analyzed 20something.be page load time and found that the first response time was 444 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
20something.be performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value9.1 s
1/100
25%
Value9.0 s
15/100
10%
Value200 ms
90/100
30%
Value0.353
31/100
15%
Value7.9 s
44/100
10%
444 ms
163 ms
244 ms
331 ms
173 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 82% of them (49 requests) were addressed to the original 20something.be, 10% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (954 ms) belongs to the original domain 20something.be.
Page size can be reduced by 1.6 MB (65%)
2.5 MB
876.7 kB
In fact, the total size of 20something.be main page is 2.5 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. 55% of websites need less resources to load. CSS take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 43.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 43.6 kB or 82% of the original size.
Potential reduce by 24.6 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. 20 Something images are well optimized though.
Potential reduce by 403.7 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 403.7 kB or 71% of the original size.
Potential reduce by 1.2 MB
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. 20something.be needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 90% of the original size.
Number of requests can be reduced by 36 (75%)
48
12
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 20 Something. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
20something.be
444 ms
wp-emoji-release.min.js
163 ms
flick.css
244 ms
20something.be
331 ms
avatar-manager.min.css
173 ms
styles.css
178 ms
lightbox.min.css
168 ms
media.css
259 ms
styles.css
463 ms
theme-icons.css
365 ms
css
26 ms
style.css
279 ms
custom.css
340 ms
wpgform.css
352 ms
js_composer.css
676 ms
components-production.min.css
499 ms
theme-options-production.css
435 ms
jquery.js
621 ms
jquery-migrate.min.js
454 ms
scrollTo.js
534 ms
jquery.form.min.js
554 ms
mailchimp.js
553 ms
core.min.js
594 ms
datepicker.js
767 ms
avatar-manager.min.js
764 ms
swfobject.js
652 ms
scripts.js
718 ms
wp-lightbox-2.min.js
719 ms
widget.min.js
737 ms
position.min.js
754 ms
menu.min.js
753 ms
autocomplete.min.js
779 ms
smoothscroll.js
780 ms
comment-reply.min.js
794 ms
scripts.js
954 ms
wp-embed.min.js
836 ms
js_composer_front.js
833 ms
components-production.min.js
862 ms
apple-touch-icon-120x120.png
131 ms
983830_866628636702005_6627271248948812211_n.jpg
397 ms
unnamed-401-micluiflycy6otrp7pr7l1a34oc737fy4nr93fjcto-micluzcpddlcht34gx2hvzthf97vpjob2cliiwg1bg.jpg
382 ms
thumb22-lu78j8ef4v3mjz580ivr76lno3dy3iiyh76vmnpx2k-mh8xlske8jc67vf6qk0jtxyn1hzver016w88wp81ik.jpg
453 ms
bair-partyflight-prev-lu77lksgff10um15jh5nf6chyf9thnwy6ma00zmdv0-mh8xnvrhfa740odyjgipdezikbp8ijak58f3au4jos.jpg
541 ms
LOGO_TS_NB-1.jpg
469 ms
BannerLOG-mgo12zi2sk2chobx0wlh6mwl57xvkn09chfvx1ffsc-mgo18t434m1aepvg0x7a6qth7sft0xhlco0oq8eeuk.jpg
481 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
13 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
15 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
14 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
14 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
14 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
12 ms
fontawesome-webfont.woff
507 ms
analytics.js
113 ms
ui-bg_flat_75_ffffff_40x100.png
110 ms
collect
13 ms
collect
65 ms
ga-audiences
38 ms
jquery.flexslider.js
101 ms
fonts-icomoon.woff
672 ms
theme-icons.woff
105 ms
20something.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
Image elements do not have [alt] attributes
20something.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
20something.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 20something.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that 20something.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.
20something.be
Open Graph description is not detected on the main page of 20 Something. 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: