1.9 sec in total
270 ms
1.4 sec
170 ms
Visit mytweets.nl now to see the best up-to-date My Tweets content and also check out these interesting facts you probably never knew about mytweets.nl
MyTweets.nl - De laatste tweets van al je favoriete personen op één pagina
Visit mytweets.nlWe analyzed Mytweets.nl page load time and found that the first response time was 270 ms and then it took 1.6 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.
mytweets.nl performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value5.6 s
18/100
25%
Value11.1 s
6/100
10%
Value22,350 ms
0/100
30%
Value0.003
100/100
15%
Value31.0 s
0/100
10%
270 ms
369 ms
87 ms
166 ms
58 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 38% of them (20 requests) were addressed to the original Mytweets.nl, 11% (6 requests) were made to Googleads.g.doubleclick.net and 9% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (450 ms) relates to the external source Nl.ads.justpremium.com.
Page size can be reduced by 138.1 kB (45%)
309.8 kB
171.7 kB
In fact, the total size of Mytweets.nl main page is 309.8 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. 55% of websites need less resources to load. Javascripts take 239.4 kB which makes up the majority of the site volume.
Potential reduce by 31.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 31.6 kB or 78% of the original size.
Potential reduce by 2.0 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. My Tweets images are well optimized though.
Potential reduce by 101.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 101.6 kB or 42% of the original size.
Potential reduce by 2.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. Mytweets.nl needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 83% of the original size.
Number of requests can be reduced by 26 (52%)
50
24
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Tweets. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
mytweets.nl
270 ms
www.mytweets.nl
369 ms
mytweets.css
87 ms
wordcloud.css
166 ms
plusone.js
58 ms
anywhere.js
23 ms
show_ads.js
23 ms
111111
112 ms
brand
44 ms
js
24 ms
js.php
450 ms
brand
30 ms
cb=gapi.loaded_0
47 ms
ca-pub-2350395255628578.js
144 ms
zrt_lookup.html
140 ms
show_ads_impl.js
59 ms
111111
140 ms
valid-html401-blue
129 ms
ga.js
29 ms
bg_left.jpg
129 ms
bg_right.jpg
128 ms
background.jpg
215 ms
mytweets.gif
202 ms
rss.gif
216 ms
bligg.gif
201 ms
delicious.gif
202 ms
digg.gif
202 ms
ekudos.gif
286 ms
facebook.gif
285 ms
google.gif
287 ms
msnreporter.gif
289 ms
nujij.gif
321 ms
stumbleupon.gif
320 ms
symbaloo.gif
380 ms
twitter.gif
381 ms
google_custom_search_watermark.gif
139 ms
ads
183 ms
__utm.gif
36 ms
osd.js
19 ms
ads
244 ms
ads
229 ms
ads
204 ms
in.php
129 ms
tracking.gif
194 ms
288 ms
abg.js
24 ms
12021487946024393427
19 ms
s
16 ms
m_js_controller.js
16 ms
x_button_blue2.png
80 ms
googlelogo_color_112x36dp.png
86 ms
nessie_icon_tiamat_white.png
28 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
5 ms
mytweets.nl accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
The document uses <meta http-equiv="refresh">
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
mytweets.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
mytweets.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 doesn't use legible font sizes
NL
NL
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mytweets.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Mytweets.nl main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
mytweets.nl
Open Graph description is not detected on the main page of My Tweets. 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: