Page load speed analysis
Visit rub.im now to see the best up-to-date Rub content and also check out these interesting facts you probably never knew about rub.im
We analyzed Rub.im page load time and found that the first response time was 474 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
Total page load time
Network requests diagram
Our browser made a total of 85 requests to load all elements on the main page. We found that 41% of them (35 requests) were addressed to the original Rub.im, 39% (33 requests) were made to Static.xx.fbcdn.net and 12% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (654 ms) relates to the external source Static.xx.fbcdn.net.
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 12.6 kB or 73% of the original size.
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. Rub images are well optimized though.
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. Rub.im needs all CSS files to be minified and compressed as it can save up to 21.7 kB or 81% of the original size.
Possible request optimization
Rub.im uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.
Language and encoding
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rub.im can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Rub.im 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.
Rub.im has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.
Visitor World Map
The server of Rub.im is located in United Kingdom, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.
Social Sharing Optimization
Open Graph description is not detected on the main page of Rub. 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:
Analyze another website