10.4 sec in total
826 ms
9.2 sec
450 ms
Click here to check amazing RIMES content for India. Otherwise, check out these important facts you probably never knew about rimes.int
Visit rimes.intWe analyzed Rimes.int page load time and found that the first response time was 826 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
rimes.int performance score
name
value
score
weighting
Value24.4 s
0/100
10%
Value32.8 s
0/100
25%
Value36.1 s
0/100
10%
Value130 ms
96/100
30%
Value2.516
0/100
15%
Value30.6 s
0/100
10%
826 ms
64 ms
563 ms
564 ms
565 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 89% of them (117 requests) were addressed to the original Rimes.int, 5% (7 requests) were made to Maps.googleapis.com and 4% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Rimes.int.
Page size can be reduced by 959.8 kB (19%)
5.0 MB
4.1 MB
In fact, the total size of Rimes.int main page is 5.0 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. 45% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 59.1 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 59.1 kB or 84% of the original size.
Potential reduce by 166.3 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. RIMES images are well optimized though.
Potential reduce by 507.1 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 507.1 kB or 69% of the original size.
Potential reduce by 227.2 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. Rimes.int needs all CSS files to be minified and compressed as it can save up to 227.2 kB or 85% of the original size.
Number of requests can be reduced by 91 (73%)
125
34
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RIMES. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 43 to 1 for CSS and as a result speed up the page load time.
rimes.int
826 ms
js
64 ms
system.base.css
563 ms
system.menus.css
564 ms
system.messages.css
565 ms
system.theme.css
566 ms
calendar_multiday.css
568 ms
comment.css
570 ms
date.css
826 ms
datepicker.1.7.css
827 ms
field.css
828 ms
node.css
829 ms
poll.css
830 ms
search.css
832 ms
shortcodes.css
1089 ms
user.css
1091 ms
forum.css
1092 ms
views.css
1092 ms
tm_lazyload.css
1094 ms
caption-filter.css
1102 ms
cctags.css
1353 ms
colorbox.css
1354 ms
ctools.css
1355 ms
panels.css
1356 ms
animate.css
1360 ms
font-awesome.css
1371 ms
flexible.css
1616 ms
date_views.css
1617 ms
ff9d510de372305971e44400273a79e4.css
1620 ms
flexslider_img.css
1620 ms
flexslider.css
1626 ms
dismiss.base.css
1635 ms
tm_follow.css
1879 ms
superfish.css
1881 ms
superfish-navbar.css
1884 ms
boilerplate.css
1885 ms
style.css
1898 ms
maintenance-page.css
1901 ms
style-mobile.css
277 ms
skeleton-mobile.css
542 ms
skeleton.css
1587 ms
custom.css
1591 ms
jquery.min.js
1864 ms
jquery.once.js
1592 ms
drupal.js
1601 ms
jquery.cookie.js
1606 ms
jquery.form.min.js
1588 ms
ajax.js
1594 ms
jquery_update.js
1594 ms
jquery.easypiechart.js
1611 ms
jquery.appear.js
1614 ms
shortcodes.js
1851 ms
jquery.lazyloader.js
1596 ms
caption-filter.js
1597 ms
jquery.colorbox-min.js
1602 ms
colorbox.js
1609 ms
image_caption.min.js
1615 ms
wow.js
1844 ms
base.js
1597 ms
progress.js
1599 ms
ajax_view.js
1604 ms
jquery.flexslider-min.js
1612 ms
tm_block_bg_video.js
1614 ms
jquery.mb.YTPlayer.js
1844 ms
jquery.stellar.min.js
1600 ms
tm_block_bg_parallax.js
1607 ms
jquery.hoverIntent.minified.js
1605 ms
superfish.js
1614 ms
jquery.easing.js
1617 ms
supersubs.js
1846 ms
superfish.js
1601 ms
theme945.core.js
1601 ms
jquery.loader.js
1606 ms
jquery.debouncedresize.js
1613 ms
css
13 ms
css
24 ms
css
25 ms
jquery.mobilemenu.js
1610 ms
jquery.easing.js
1843 ms
jquery.ui.totop.js
1603 ms
jquery.cookie.js
1598 ms
tm-stick-up.js
1604 ms
tformer.js
1606 ms
device.min.js
1609 ms
jquery.mousewheel.min.js
1600 ms
jquery.simplr.smoothscroll.min.js
1596 ms
migrate.js
1597 ms
flexslider.load.js
1657 ms
header-img.jpg
1079 ms
Inaguartion.jpg
1324 ms
radar_station_0.jpg
828 ms
wangdue_0.jpg
1941 ms
header-img_0.jpg
1647 ms
sc2_0.jpg
1087 ms
Sittwe-Myanmar_0.png
1647 ms
buoy-seyc.jpg
1367 ms
logo.png
1352 ms
bg-1.gif
1591 ms
Santa%20Phil%20Seismic%20Station%20%281%29.JPG
1624 ms
A00_2237.JPG
1640 ms
climate_dev.png
4235 ms
title-13.png
1894 ms
societal.png
1912 ms
earthquake.png
1930 ms
weather.png
1929 ms
water2.png
2178 ms
seasonal.png
2190 ms
climate.png
2201 ms
title-21.png
2199 ms
DSC_5122.JPG
2206 ms
2017-08-23-PHOTO-00000002.jpg
2444 ms
DSC_0206.png
2765 ms
Nepal-MOU.jpg
2476 ms
title-22.png
2474 ms
sesame_google_play_for_rimes.png
2498 ms
li_bullet.gif
2656 ms
th-calendar.png
2687 ms
WoAoVT7K3k7hHfxKbvB6B0BTuPGxyeV-VBVV8KqqzrI.woff
75 ms
4iCv6KVjbNBYlgoCxCvjsGyL.woff
75 ms
4iCv6KVjbNBYlgoCjC3jsGyL.woff
75 ms
4iCs6KVjbNBYlgoKfw7w.woff
75 ms
4iCv6KVjbNBYlgoC1CzjsGyL.woff
75 ms
fontawesome-webfont.woff
2677 ms
list-marker.png
2697 ms
list-marker-sm.png
2899 ms
overlay.png
2880 ms
common.js
4 ms
util.js
14 ms
stats.js
21 ms
AuthenticationService.Authenticate
120 ms
map.js
6 ms
marker.js
5 ms
rimes.int 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
rimes.int 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
rimes.int SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Rimes.int 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 Rimes.int 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.
rimes.int
Open Graph description is not detected on the main page of RIMES. 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: