Tools & Wizards About Us
premotion.at screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

premotion.at

Premotion Media Consulting - Webdevelopment and E-commerce Consulting - Premotion

Page Load Speed

5.2 sec in total

First Response

365 ms

Resources Loaded

3.3 sec

Page Rendered

1.5 sec

premotion.at screenshot

About Website

Click here to check amazing Premotion content. Otherwise, check out these important facts you probably never knew about premotion.at

3:45 duration

Visit premotion.at

Key Findings

We analyzed Premotion.at page load time and found that the first response time was 365 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.

Performance Metrics

premotion.at performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

premotion.at

365 ms

css

25 ms

skeleton.css

216 ms

style.css

218 ms

supersized.css

224 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 64% of them (49 requests) were addressed to the original Premotion.at, 5% (4 requests) were made to F.vimeocdn.com and 4% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Premotion.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 679.4 kB (25%)

Content Size

2.7 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Premotion.at main page is 2.7 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. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 27.4 kB

  • Original 39.1 kB
  • After minification 36.4 kB
  • After compression 11.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 27.4 kB or 70% of the original size.

Image Optimization

-7%

Potential reduce by 142.0 kB

  • Original 2.0 MB
  • After minification 1.8 MB

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. Premotion images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 346.8 kB

  • Original 489.1 kB
  • After minification 455.7 kB
  • After compression 142.3 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 346.8 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 163.2 kB

  • Original 189.0 kB
  • After minification 167.6 kB
  • After compression 25.8 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. Premotion.at needs all CSS files to be minified and compressed as it can save up to 163.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (63%)

Requests Now

70

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

premotion.at

premotion.at

365 ms

css

css

25 ms

skeleton.css

skeleton.css

216 ms

style.css

style.css

218 ms

supersized.css

supersized.css

224 ms

supersized.shutter.css

supersized.shutter.css

223 ms

jquery.fancybox.css

jquery.fancybox.css

225 ms

font-awesome.css

font-awesome.css

227 ms

flexslider.css

flexslider.css

430 ms

media.css

media.css

433 ms

jquery.min.js

jquery.min.js

11 ms

jquery.easing.min.js

jquery.easing.min.js

443 ms

supersized.3.2.7.min.js

supersized.3.2.7.min.js

443 ms

supersized.shutter.min.js

supersized.shutter.min.js

444 ms

supersized.images.js

supersized.images.js

444 ms

main.js

main.js

659 ms

jquery.parallax-1.1.3.js

jquery.parallax-1.1.3.js

657 ms

jquery.tweet.js

jquery.tweet.js

661 ms

twitter-options.js

twitter-options.js

662 ms

paralax-ini.js

paralax-ini.js

661 ms

scroll.js

scroll.js

663 ms

jquery.flexslider.js

jquery.flexslider.js

871 ms

selectnav.min.js

selectnav.min.js

873 ms

jquery.isotope.min.js

jquery.isotope.min.js

873 ms

jquery.smartresize.js

jquery.smartresize.js

898 ms

shortcodes.js

shortcodes.js

899 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

900 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

1082 ms

jquery.sticky.js

jquery.sticky.js

1090 ms

contact.js

contact.js

1089 ms

fbds.js

fbds.js

9 ms

logo.png

logo.png

1224 ms

claim.png

claim.png

1540 ms

map.png

map.png

1346 ms

sdk.js

sdk.js

45 ms

pattern.png

pattern.png

1220 ms

homepage_background.png

homepage_background.png

1219 ms

nav-bg.png

nav-bg.png

1221 ms

teaser1.jpg

teaser1.jpg

1222 ms

quote.png

quote.png

1220 ms

teaser2.jpg

teaser2.jpg

1294 ms

twitter-widget-localcached.js

twitter-widget-localcached.js

1188 ms

121 ms

teaser3.jpg

teaser3.jpg

1472 ms

contacts.jpg

contacts.jpg

1793 ms

contact-bg.png

contact-bg.png

1389 ms

social-icons-bg.png

social-icons-bg.png

1471 ms

footer-gr.png

footer-gr.png

1508 ms

96115051

96115051

89 ms

68537433

68537433

113 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

60 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

61 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1718 ms

-g5pDUSRgvxvOl5u-a_WHw.woff

-g5pDUSRgvxvOl5u-a_WHw.woff

61 ms

BebasNeue-webfont.woff

BebasNeue-webfont.woff

1684 ms

180 ms

xd_arbiter.php

xd_arbiter.php

27 ms

xd_arbiter.php

xd_arbiter.php

39 ms

player.js

player.js

120 ms

player.css

player.css

99 ms

ga.js

ga.js

53 ms

vuid.min.js

vuid.min.js

95 ms

__utm.gif

__utm.gif

32 ms

__utm.gif

__utm.gif

12 ms

proxy.html

proxy.html

40 ms

476568645.webp

476568645.webp

112 ms

440899449.webp

440899449.webp

73 ms

image4.jpg

image4.jpg

1050 ms

image1.jpg

image1.jpg

1310 ms

image6.jpg

image6.jpg

1323 ms

progress.gif

progress.gif

729 ms

follow_button.1372833608.html

follow_button.1372833608.html

98 ms

jot

jot

83 ms

like.php

like.php

120 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

26 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

19 ms

Accessibility Review

premotion.at accessibility score

42

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

premotion.at best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

premotion.at SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

premotion.at

Open Graph description is not detected on the main page of Premotion. 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: