Tools & Wizards About Us
viking.at screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

viking.at

Startseite | STIHL

Page Load Speed

2.6 sec in total

First Response

331 ms

Resources Loaded

2 sec

Page Rendered

307 ms

viking.at screenshot

About Website

Visit viking.at now to see the best up-to-date Viking content for Austria and also check out these interesting facts you probably never knew about viking.at

STIHL - Information rund um das Unternehmen STIHL und das vielfältige Produktsortiment der Motorsägen und Motorgeräte: Motorsäge, Kettensägen, Motorsensen, Heckenscheren, Trennschleifer, Blasgeräte, R...

Visit viking.at

Key Findings

We analyzed Viking.at page load time and found that the first response time was 331 ms and then it took 2.3 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.

Performance Metrics

viking.at performance score

0

Network Requests Diagram

viking.at

331 ms

www.viking.at

365 ms

screen.min.css

139 ms

lib.min.js

165 ms

custom.min.js

135 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 22% of them (11 requests) were addressed to the original Viking.at, 52% (26 requests) were made to Static.viking-garden.com and 8% (4 requests) were made to Wm.wiredminds.de. The less responsive or slowest element that took the longest time to load (918 ms) belongs to the original domain Viking.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 598.8 kB (37%)

Content Size

1.6 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Viking.at main page is 1.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. 50% of websites need less resources to load. Images take 855.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 18.4 kB

  • Original 24.1 kB
  • After minification 18.9 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 5.2 kB, which is 22% 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 18.4 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 12.2 kB

  • Original 855.4 kB
  • After minification 843.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. Viking images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 315.1 kB

  • Original 459.5 kB
  • After minification 428.4 kB
  • After compression 144.5 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 315.1 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 253.2 kB

  • Original 296.3 kB
  • After minification 238.4 kB
  • After compression 43.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. Viking.at needs all CSS files to be minified and compressed as it can save up to 253.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (47%)

Requests Now

45

After Optimization

24

  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viking. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

viking.at

viking.at

331 ms

www.viking.at

www.viking.at

365 ms

screen.min.css

screen.min.css

139 ms

lib.min.js

lib.min.js

165 ms

custom.min.js

custom.min.js

135 ms

count.js

count.js

315 ms

viking_overlay_fruehling_2012.jpg

viking_overlay_fruehling_2012.jpg

918 ms

gtm.js

gtm.js

47 ms

header_teaser_text.png

header_teaser_text.png

232 ms

Neuheiten_2016_VIKING_600x600.jpg

Neuheiten_2016_VIKING_600x600.jpg

199 ms

slider-service-vor-der-gartensaison.jpg

slider-service-vor-der-gartensaison.jpg

399 ms

slider-film-fruehling.jpg

slider-film-fruehling.jpg

15 ms

slider-film-imow-robotermaeher-magic.jpg

slider-film-imow-robotermaeher-magic.jpg

310 ms

putz_small-teaser_290x180_rdax_90.jpg

putz_small-teaser_290x180_rdax_90.jpg

124 ms

fachhaendler_290x180_rdax_90.jpg

fachhaendler_290x180_rdax_90.jpg

130 ms

stihl_viking_rdax_90.jpg

stihl_viking_rdax_90.jpg

135 ms

fade.png

fade.png

130 ms

fachhaendler.png

fachhaendler.png

134 ms

arrow_down.png

arrow_down.png

129 ms

contact.jpg

contact.jpg

129 ms

viking_logo.jpg

viking_logo.jpg

232 ms

viking_print_logo.gif

viking_print_logo.gif

220 ms

nav_back.jpg

nav_back.jpg

246 ms

icon_search.png

icon_search.png

252 ms

search_send.jpg

search_send.jpg

243 ms

social-linklist-icon_facebook.png

social-linklist-icon_facebook.png

250 ms

social-linklist-icon_google.png

social-linklist-icon_google.png

347 ms

social-linklist-icon_youtube.png

social-linklist-icon_youtube.png

355 ms

arrow_link.png

arrow_link.png

360 ms

page_arrow_left.png

page_arrow_left.png

356 ms

page_arrow_right.png

page_arrow_right.png

363 ms

arrow_right_green.png

arrow_right_green.png

362 ms

submit_arrow_right.gif

submit_arrow_right.gif

457 ms

icon_print.png

icon_print.png

462 ms

comment.png

comment.png

474 ms

icon_sm.png

icon_sm.png

541 ms

green_arrow.png

green_arrow.png

542 ms

orange_arrow.png

orange_arrow.png

542 ms

analytics.js

analytics.js

7 ms

gtmext.min.js

gtmext.min.js

55 ms

linkid.js

linkid.js

22 ms

count.js

count.js

401 ms

collect

collect

18 ms

collect

collect

66 ms

collect

collect

19 ms

ga-audiences

ga-audiences

50 ms

ga-audiences

ga-audiences

44 ms

ctin.php

ctin.php

185 ms

print.min.css

print.min.css

4 ms

ctin.php

ctin.php

333 ms

SEO Factors

viking.at SEO score

0

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viking.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Viking.at 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.

Social Sharing Optimization

viking.at

Open Graph data is detected on the main page of Viking. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: