1.2 sec in total
223 ms
770 ms
191 ms
Click here to check amazing Twitto content. Otherwise, check out these important facts you probably never knew about twitto.be
Twitto is a live analytics dashboard of the tweets related to entrepreneurship in Belgium. Curious about the trending topics right now? Come have a look.
Visit twitto.beWe analyzed Twitto.be page load time and found that the first response time was 223 ms and then it took 961 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
twitto.be performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.3 s
93/100
25%
Value11.3 s
5/100
10%
Value10,160 ms
0/100
30%
Value0.223
56/100
15%
Value17.5 s
4/100
10%
223 ms
175 ms
165 ms
166 ms
166 ms
Our browser made a total of 14 requests to load all elements on the main page. We found that 71% of them (10 requests) were addressed to the original Twitto.be, 14% (2 requests) were made to Google-analytics.com and 7% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (346 ms) belongs to the original domain Twitto.be.
Page size can be reduced by 162.7 kB (45%)
358.2 kB
195.5 kB
In fact, the total size of Twitto.be main page is 358.2 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. Images take 153.7 kB which makes up the majority of the site volume.
Potential reduce by 3.5 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 3.5 kB or 65% of the original size.
Potential reduce by 2.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. Twitto images are well optimized though.
Potential reduce by 32.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 32.0 kB or 60% of the original size.
Potential reduce by 125.0 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. Twitto.be needs all CSS files to be minified and compressed as it can save up to 125.0 kB or 86% of the original size.
Number of requests can be reduced by 3 (25%)
12
9
The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Twitto. 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.
twitto.be
223 ms
twitto-bootstrap.css
175 ms
bootstrap-responsive.css
165 ms
custom.css
166 ms
twitto_be-0.4.0-square-logo-40x40.png
166 ms
social_twitter_circle_color.png
167 ms
social_google_circle_color.png
171 ms
social_facebook_circle_color.png
258 ms
social_linkedin_circle_color.png
257 ms
css
24 ms
analytics.js
4 ms
bg.jpg
346 ms
collect
18 ms
2Q-AW1e_taO6pHwMXcXW5w.ttf
6 ms
twitto.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
twitto.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
twitto.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Twitto.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 Twitto.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.
twitto.be
Open Graph data is detected on the main page of Twitto. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: