10.2 sec in total
311 ms
9 sec
923 ms
Visit tallinksilja.no now to see the best up-to-date Tallink Silja content for Norway and also check out these interesting facts you probably never knew about tallinksilja.no
Fergetur fra Stockholm til mange ulike destinasjoner. Bestill reise enkelt med Tallink & Silja Line. Blir kjent med våre destinasjoner, Helsingfors, Åbo, Åland, Tallinn og Riga.
Visit tallinksilja.noWe analyzed Tallinksilja.no page load time and found that the first response time was 311 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tallinksilja.no performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value28.8 s
0/100
25%
Value17.4 s
0/100
10%
Value850 ms
34/100
30%
Value0.124
83/100
15%
Value28.6 s
0/100
10%
311 ms
1131 ms
591 ms
235 ms
233 ms
Our browser made a total of 193 requests to load all elements on the main page. We found that 85% of them (164 requests) were addressed to the original Tallinksilja.no, 5% (9 requests) were made to Booking.tallink.com and 2% (4 requests) were made to Secure.livechatinc.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Tallinksilja.no.
Page size can be reduced by 2.0 MB (56%)
3.6 MB
1.6 MB
In fact, the total size of Tallinksilja.no main page is 3.6 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. 65% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 131.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. This page needs HTML code to be minified as it can gain 52.5 kB, which is 35% 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 131.5 kB or 88% of the original size.
Potential reduce by 55.2 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. Tallink Silja images are well optimized though.
Potential reduce by 1.1 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.1 MB or 71% of the original size.
Potential reduce by 755.1 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. Tallinksilja.no needs all CSS files to be minified and compressed as it can save up to 755.1 kB or 86% of the original size.
Number of requests can be reduced by 155 (83%)
187
32
The browser has sent 187 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tallink Silja. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 98 to 1 for CSS and as a result speed up the page load time.
www.tallinksilja.no
311 ms
finn-reise
1131 ms
aui.css
591 ms
main.css
235 ms
main.css
233 ms
main.css
358 ms
main.css
252 ms
barebone.jsp
858 ms
main.js
456 ms
navigation.js
341 ms
main.js
365 ms
main.js
496 ms
main.css
475 ms
bookingEntry.css
834 ms
require.min.js
732 ms
jquery.animate-enhanced.min.js
321 ms
jquery.flexslider-min.js
353 ms
jquery.lazyload.min.js
387 ms
storyjs-embed.js
410 ms
jquery.dd.js
439 ms
jquery.fancybox-2.0.3.min.js
463 ms
jquery.ui.datepicker.min.js
488 ms
jquery-ui-autocomplete.min.js
605 ms
jquery.ui.core.min.js
520 ms
plugins.js
572 ms
script.js
590 ms
main.js
607 ms
aui_deprecated.css
627 ms
portal_1.css
680 ms
portal_2.css
690 ms
taglib_1.css
708 ms
taglib_2.css
710 ms
accessibility.css
732 ms
add_content.css
118 ms
asset_category_selector.css
122 ms
asset_column.css
139 ms
auto_row.css
151 ms
device_preview.css
155 ms
edit_layout.css
169 ms
flyout.css
238 ms
forms.css
255 ms
generic_portal.css
257 ms
generic_portlet.css
264 ms
header_row.css
266 ms
javascript_template.css
280 ms
notifications.css
349 ms
openid.css
370 ms
page_settings.css
367 ms
panel_component.css
379 ms
panel_page.css
382 ms
pagination.css
390 ms
panel_pagination.css
453 ms
portlet_css_editor.css
475 ms
portlet_item.css
478 ms
position_helper.css
487 ms
preview.css
490 ms
rich_editor.css
496 ms
search_combobox.css
562 ms
separator.css
584 ms
tag_selector.css
592 ms
toolbar.css
623 ms
translation_manager.css
605 ms
tree.css
611 ms
undo_manager.css
675 ms
uploader.css
718 ms
app_view_common.css
730 ms
app_view_entry.css
732 ms
app_view_navigation_item.css
726 ms
app_view_search_entry.css
714 ms
app_view_toolbar.css
693 ms
asset_categories_summary.css
734 ms
asset_links.css
1733 ms
button.css
734 ms
calendar.css
729 ms
captcha.css
718 ms
categorization_filter.css
689 ms
ddm_template.css
707 ms
diff.css
753 ms
diff_html.css
753 ms
discussion.css
748 ms
flags.css
761 ms
form_navigator.css
726 ms
header.css
758 ms
icon.css
757 ms
icon_help.css
747 ms
icon_list.css
768 ms
icon_menu.css
796 ms
input_localized.css
782 ms
input_move_boxes.css
758 ms
field_wrapper.css
758 ms
input_permissions.css
767 ms
input_repeat.css
802 ms
language.css
847 ms
logo_selector.css
783 ms
navbar.css
761 ms
preview.css
777 ms
ratings.css
798 ms
rss_settings.css
857 ms
search_container.css
844 ms
search_iterator.css
793 ms
search_toggle.css
762 ms
sites_directory.css
770 ms
social_activities.css
839 ms
social_bookmarks.css
834 ms
tags_summary.css
833 ms
trash_common.css
794 ms
user_display.css
783 ms
webdav.css
830 ms
workflow_status.css
835 ms
base.css
111 ms
application.css
117 ms
layout.css
116 ms
dockbar.css
112 ms
navigation.css
120 ms
portlet.css
121 ms
extras.css
335 ms
custom.css
377 ms
jquery-1.8.3.min.js
557 ms
Bootstrap.js
36 ms
serverComponent.php
18 ms
70c426476036875f2921ba5ed7ea725a.js
5 ms
fbevents.js
8 ms
analytics.js
25 ms
102 ms
jquery.cookie.js
171 ms
easyXDM.min.js
125 ms
bg_nav_1st.png
153 ms
bg_nav_1st_link.png
159 ms
bg_nav_1st_link_active.png
154 ms
bg_nav_1st_login.png
158 ms
spacer.png
160 ms
search.png
161 ms
d1b44403-e2b2-4e06-a479-0a1cda8cbbb2
1339 ms
b40b92d7-7f52-4b4c-9aa3-7d96b6345afc
643 ms
aacbf072-e404-4288-aa30-3e45ba702838
1383 ms
27d2c87f-49c1-4a98-bf93-c02da80a8b65
1798 ms
8ce53b29-c3a5-4049-8dfc-35a5ec5fd64c
1068 ms
white.gif
337 ms
0eaf1c70-f77a-4b65-a76f-503cd399ec7c
707 ms
899cb807-c9b1-4fa7-9f88-d045cb317035
1048 ms
001516a3-6953-46b9-935a-6d9cfe01ca6e
990 ms
3a80e49f-2c3a-4a81-9424-e8998ae50344
1439 ms
StagSansLCWeb-Book.woff
2267 ms
StagSansLCWeb-Medium.woff
2154 ms
layout_set_logo
1569 ms
bg_nav_2nd_link.png
1508 ms
bg_nav_2nd_link_active.png
1746 ms
bg_nav_2nd_marker.png
1644 ms
bg_nav_2nd_link_clubone.png
1710 ms
bg_nav_3rd_shadow.png
1789 ms
bg_nav_3rd_li.gif
1850 ms
bg_nav_4th_bg_bottom.png
1894 ms
main.js
117 ms
bg_fp_carousel_mid.png
1906 ms
bg_top_lmo.png
1927 ms
bg_section_alt_top.png
1989 ms
shadow_outer_top_tabs.png
2050 ms
bg_seperator940.gif
2068 ms
sprites.png
2380 ms
bg_footer.png
2150 ms
shadow_outer_top.png
2200 ms
icons_footer.png
2260 ms
StagSansLCWeb-Light.woff
2523 ms
tracking.js
78 ms
collect
44 ms
5174.js
120 ms
2211 ms
bookingEntry.js
435 ms
bg_control_nav.png
2252 ms
bg_direction_nav.png
2256 ms
72a0cf18-f767-40c3-91f7-6a6bc1a5c6ea
2278 ms
cd7ad7b9-a908-47d7-8172-7c68df333049
2344 ms
03a494c9-8a64-43d5-b4bb-1f37c743454e
2544 ms
script_data.js
104 ms
s
89 ms
u
88 ms
localization.nb.0.0f522b3271d1ec1cd7cb108caab42a0b_b6f9653172d517ed6bbd2ecdfae1e648.js
66 ms
ping
100 ms
open_chat.cgi
96 ms
livechat-classic_f726105e9a.ttf
30 ms
embedded.20160310142511.js
102 ms
common.js
109 ms
booking.js
112 ms
like.php
238 ms
spinner-s64a449eeb6.png
194 ms
search-button-left.png
110 ms
search-button-right.png
112 ms
fy8tT2klpgR.js
51 ms
LVx-xkvaJ0b.png
46 ms
176 ms
191 ms
available_languages.jsp
246 ms
285 ms
tallinksilja.no 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
Image elements do not have [alt] attributes
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
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.
tallinksilja.no 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
tallinksilja.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
NO
TA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tallinksilja.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed Tamil language. Our system also found out that Tallinksilja.no 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.
tallinksilja.no
Open Graph description is not detected on the main page of Tallink Silja. 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: