3.8 sec in total
500 ms
3.2 sec
105 ms
Click here to check amazing Swalo content for Germany. Otherwise, check out these important facts you probably never knew about swalo.de
Tomtom Ticket.
Visit swalo.deWe analyzed Swalo.de page load time and found that the first response time was 500 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.
swalo.de performance score
500 ms
338 ms
342 ms
362 ms
227 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 87% of them (82 requests) were addressed to the original Swalo.de, 3% (3 requests) were made to Stmticket.de and 2% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Swalo.de.
Page size can be reduced by 1.5 MB (79%)
1.8 MB
382.1 kB
In fact, the total size of Swalo.de main page is 1.8 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 58.0 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. This page needs HTML code to be minified as it can gain 8.8 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 58.0 kB or 85% of the original size.
Potential reduce by 19.9 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, Swalo needs image optimization as it can save up to 19.9 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.2 MB
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 1.2 MB or 80% of the original size.
Potential reduce by 197.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. Swalo.de needs all CSS files to be minified and compressed as it can save up to 197.9 kB or 81% of the original size.
Number of requests can be reduced by 80 (90%)
89
9
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Swalo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
swalo.de
500 ms
normalize.css
338 ms
a_tomtom-dev.css
342 ms
m_tomtom.css
362 ms
stm_styles.css
227 ms
mro.spinnerdropdown.css
253 ms
ma_tomtom.css
333 ms
ma_tomtom-dev.css
340 ms
bootstrap-combined.min.css
38 ms
bootstrap-select.css
374 ms
styles.css
455 ms
olkaStyles.css
466 ms
jquery-ui.css
595 ms
jquery.fancybox.css
467 ms
reveal.css
479 ms
mroautocomplete.css
567 ms
swazzcalendar.css
579 ms
WebResource.axd
575 ms
ScriptResource.axd
603 ms
ScriptResource.axd
612 ms
js
588 ms
js
584 ms
FlightSearchInputForm.js
589 ms
json2.js
510 ms
jquery-1.9.1.js
1039 ms
jquery-migrate-1.2.1.js
604 ms
jquery-ui.js
1063 ms
jquery.jmpopups-0.5.1.js
628 ms
jquery.cookie.js
642 ms
jquery.fancybox.js
637 ms
jquery.multiselect.js
747 ms
jquery.loadmask.js
748 ms
jquery.ui.datepicker-de.js
764 ms
jquery-ui-timepicker-addon.js
881 ms
jquery-ui-timepicker-de.js
858 ms
jquery.reveal.js
864 ms
js
88 ms
step1.js
231 ms
lodash.backbone.js
1001 ms
pubsub.js
985 ms
mro.js
950 ms
mro.dom.js
896 ms
mro.xml.js
994 ms
mro.utils.js
1052 ms
mro.page.js
1052 ms
mro.object.js
991 ms
mro.ordereddictionary.js
1016 ms
mro.ui.js
922 ms
mro.autocomplete.js
991 ms
mro.global.js
1004 ms
mro.popupview.js
1017 ms
mro.message-manager.js
1019 ms
overlib.js
949 ms
mro.calendar.js
934 ms
mro.searchinput.js
995 ms
tripLeftSelected.png
222 ms
tripCenterUnselected.png
224 ms
tripRightUnselected.png
228 ms
swazzcalendar.js
994 ms
mro.flightsearchinput.js
925 ms
ClientScripts.aspx
1585 ms
bootstrap-select.js
952 ms
bootstrap.min.js
928 ms
icheck.min.js
977 ms
indexof.polyfill.js
996 ms
global-lib.js
913 ms
global.js
914 ms
mro.spinnerdropdown.js
915 ms
ga_stm.js
961 ms
m_custom-scripts.js
875 ms
geoPosition.js
880 ms
mro.location.js
893 ms
TrimWeb-Regular.woff
857 ms
TrimWeb-Light.woff
870 ms
TrimWeb-Bold.woff
761 ms
bg-header.png
776 ms
logo.png
780 ms
active.png
826 ms
bg-select.png
794 ms
clock2.png
787 ms
bg-hr.png
766 ms
bg-button.png
762 ms
partners.png
798 ms
analytics.js
7 ms
12a944f7.js
181 ms
jquery-ui.css
23 ms
collect
155 ms
spinnerDropdownMinus.png
120 ms
glyphicons-halflings.png
60 ms
ui-bg_flat_75_ffffff_40x100.png
5 ms
spinnerDropdownBoxBG.png
121 ms
spinnerDropdownPlus.png
123 ms
cal.png
113 ms
ipc8za4tass0erni0xbwv37qzdlz96d8
388 ms
swalo.de SEO score
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Swalo.de 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 Swalo.de 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.
swalo.de
Open Graph description is not detected on the main page of Swalo. 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: