5.2 sec in total
331 ms
4.1 sec
697 ms
Click here to check amazing Otillo content for United States. Otherwise, check out these important facts you probably never knew about otillo.se
The 7/24 concept will end with ÖTILLÖ, The Swimrun World Championship 2020. The last application date for 7/24 spots will be July 15, 2020.
Visit otillo.seWe analyzed Otillo.se page load time and found that the first response time was 331 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
otillo.se performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value3.1 s
75/100
25%
Value3.4 s
89/100
10%
Value250 ms
84/100
30%
Value0
100/100
15%
Value3.4 s
93/100
10%
331 ms
782 ms
242 ms
317 ms
215 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Otillo.se, 24% (21 requests) were made to Maps.googleapis.com and 23% (20 requests) were made to Otilloswimrun.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Otilloswimrun.com.
Page size can be reduced by 943.4 kB (48%)
2.0 MB
1.0 MB
In fact, the total size of Otillo.se main page is 2.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. 60% of websites need less resources to load. Javascripts take 788.7 kB which makes up the majority of the site volume.
Potential reduce by 41.7 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 41.7 kB or 79% of the original size.
Potential reduce by 13.1 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. Otillo images are well optimized though.
Potential reduce by 517.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 517.6 kB or 66% of the original size.
Potential reduce by 371.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. Otillo.se needs all CSS files to be minified and compressed as it can save up to 371.0 kB or 89% of the original size.
Number of requests can be reduced by 40 (51%)
79
39
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otillo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
otillo.se
331 ms
782 ms
242 ms
wp-emoji-release.min.js
317 ms
215 ms
css
27 ms
326 ms
jquery.js
538 ms
jquery-migrate.min.js
216 ms
gprofiles.js
53 ms
1402 ms
devicepx-jetpack.js
3 ms
e-201611.js
4 ms
style.css
1001 ms
analytics.js
33 ms
raceImg-OTILLO-About-Section01-OTILLO2015.jpg
1331 ms
raceImg-OTILLO-About-Section02-OTILLO2015.jpg
1372 ms
OOswimrunSeries-Logo-Left.png
220 ms
partnerLogo-Head.png
221 ms
partnerLogo-Campz.png
220 ms
partnerLogo-Apollo.png
249 ms
partnerLogo-UtoVardshus.png
260 ms
partnerLogo-CapitalOfScandinavia.png
261 ms
raceImg-OTILLO-About-Section03-OTILLO2015.jpg
1371 ms
sdk.js
215 ms
embed
450 ms
raceImg-OTILLO-Main-OTILLO15.jpg
1076 ms
collect
142 ms
trasandinaregular-webfont.woff
445 ms
phosphate-solid-webfont.woff
471 ms
ETmodules_v2_4.ttf
727 ms
trasandinabold-webfont.woff
491 ms
hovercard.css
41 ms
services.css
74 ms
g.gif
27 ms
113 ms
xd_arbiter.php
126 ms
xd_arbiter.php
262 ms
rs=ABjfnFWG0j3zhtsZ1FCMy39vp-nQopMVGw
61 ms
css
82 ms
js
128 ms
rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw
69 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
171 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
179 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
207 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
219 ms
rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw
90 ms
common.js
98 ms
map.js
121 ms
overlay.js
120 ms
util.js
177 ms
poly.js
175 ms
marker.js
102 ms
geocoder.js
154 ms
controls.js
154 ms
places_impl.js
152 ms
selection_2x-000.png
51 ms
gen204
140 ms
onion.js
135 ms
openhand_8_8.cur
187 ms
ViewportInfoService.GetViewportInfo
151 ms
stats.js
143 ms
kh
189 ms
kh
194 ms
StaticMapService.GetMapImage
125 ms
kh
151 ms
kh
163 ms
kh
165 ms
kh
138 ms
transparent.png
61 ms
mapcnt6.png
38 ms
undo_poly.png
37 ms
tmapctrl4.png
59 ms
vt
43 ms
vt
42 ms
vt
37 ms
vt
48 ms
vt
69 ms
vt
57 ms
vt
67 ms
viewer-icons001.png
150 ms
star4.png
180 ms
MyMaps_Icons003.png
58 ms
mymaps_32.png
58 ms
v1_4593b7d7.png
103 ms
google-my-maps-logo-small-001.png
104 ms
otillo.se 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
otillo.se best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
otillo.se 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
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 Otillo.se 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 Otillo.se 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.
otillo.se
Open Graph data is detected on the main page of Otillo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: