2.5 sec in total
126 ms
2.2 sec
195 ms
Visit runsam.com now to see the best up-to-date RUNSAM content for Canada and also check out these interesting facts you probably never knew about runsam.com
Visit runsam.comWe analyzed Runsam.com page load time and found that the first response time was 126 ms and then it took 2.4 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.
runsam.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.5 s
18/100
25%
Value10.4 s
8/100
10%
Value5,770 ms
0/100
30%
Value0.278
44/100
15%
Value27.5 s
0/100
10%
126 ms
196 ms
299 ms
86 ms
73 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that all of those requests were addressed to Runsam.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Runsam.com.
Page size can be reduced by 1.5 MB (81%)
1.9 MB
351.2 kB
In fact, the total size of Runsam.com main page is 1.9 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. 25% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 5.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 5.5 kB or 72% of the original size.
Potential reduce by 467.4 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. Obviously, RUNSAM needs image optimization as it can save up to 467.4 kB or 83% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 987.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 987.7 kB or 80% of the original size.
Potential reduce by 73.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. Runsam.com needs all CSS files to be minified and compressed as it can save up to 73.9 kB or 83% of the original size.
Number of requests can be reduced by 49 (62%)
79
30
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RUNSAM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
login.php
126 ms
css_branding.php
196 ms
prototype.js
299 ms
_lib.js
86 ms
progress.js
73 ms
navSelect.js
74 ms
scriptaculous.js
100 ms
sorttable.js
220 ms
tableEffects.js
176 ms
effects.js
269 ms
lowpro.js
204 ms
popup.js
286 ms
sink.js
263 ms
yahoo-min.js
279 ms
event-min.js
371 ms
dom-min.js
366 ms
dragdrop-min.js
416 ms
animation-min.js
426 ms
js_color_picker_v2.css
355 ms
color_functions.js
364 ms
js_color_picker_v2.js
501 ms
date-functions.js
468 ms
datechooser.js
468 ms
datechooser.css
441 ms
select-free.css
491 ms
jquery-ui.css
598 ms
jquery.qtip.css
547 ms
tagit-dark-grey.css
536 ms
jquery-2.1.1.min.js
718 ms
jquery.tablesorter.js
733 ms
jquery.tablesorter.widgets.js
787 ms
jquery.sparkline.min.js
708 ms
Chart.min.js
729 ms
tabs.js
657 ms
jquery.qtip.js
842 ms
jquery-ui.js
1132 ms
builder.js
476 ms
effects.js
606 ms
dragdrop.js
614 ms
controls.js
651 ms
slider.js
585 ms
sound.js
607 ms
dragscroller.js
654 ms
scroller.js
701 ms
drifter.js
670 ms
frame_tab_tl.png
142 ms
frame_tab_tr.png
185 ms
frame_top.png
105 ms
header-logo-glassfx.png
221 ms
main-header-glassFX.png
183 ms
syslogo.png
116 ms
wallpaper.png
320 ms
frame_left.png
294 ms
frame_right.png
206 ms
nav_top.png
355 ms
nav_right.png
362 ms
vertnav-glass.png
384 ms
nav_bottom.png
401 ms
live_conference.png
434 ms
horz-nav.gif
392 ms
frame_bottom.png
406 ms
progress_1.png
37 ms
progress_2.png
76 ms
progress_3.png
76 ms
progress_4.png
76 ms
progress_5.png
75 ms
progress_6.png
76 ms
progress_7.png
108 ms
progress_8.png
140 ms
progress_9.png
140 ms
progress_10.png
140 ms
progress_11.png
141 ms
sink_top.png
140 ms
sink_right.png
174 ms
sink_bottom.png
207 ms
sink_left.png
208 ms
sink_tl.png
210 ms
sink_tr.png
208 ms
sink_bl.png
209 ms
sink_br.png
243 ms
runsam.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
runsam.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
runsam.com SEO score
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
Tap targets are not sized appropriately
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runsam.com 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 Runsam.com 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.
runsam.com
Open Graph description is not detected on the main page of RUNSAM. 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: