Tools & Wizards About Us
slayer.film screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

slayer.film

Slayer: The Repentless Killogy: Get Tickets | Trafalgar Releasing

Page Load Speed

1.5 sec in total

First Response

13 ms

Resources Loaded

1.2 sec

Page Rendered

208 ms

slayer.film screenshot

About Website

Visit slayer.film now to see the best up-to-date Slayer content and also check out these interesting facts you probably never knew about slayer.film

Search for screenings / showtimes and book tickets for Slayer: The Repentless Killogy. See the release date and trailer. The Official Showtimes Destination brought to you by Trafalgar Releasing

Visit slayer.film

Key Findings

We analyzed Slayer.film page load time and found that the first response time was 13 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

slayer.film performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

31/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value2,750 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.217

57/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

slayer.film

13 ms

www.slayer.film

17 ms

www.slayer.film

129 ms

showtimes.css

105 ms

css

30 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 13% of them (5 requests) were addressed to the original Slayer.film, 18% (7 requests) were made to Dx35vtwkllhj9.cloudfront.net and 10% (4 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (636 ms) relates to the external source Dx35vtwkllhj9.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.6 kB (7%)

Content Size

777.8 kB

After Optimization

721.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Slayer.film main page is 777.8 kB. 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 502.8 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 54.0 kB

  • Original 80.0 kB
  • After minification 80.0 kB
  • After compression 26.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. 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 54.0 kB or 68% of the original size.

Image Optimization

-0%

Potential reduce by 530 B

  • Original 502.8 kB
  • After minification 502.3 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. Slayer images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.2 kB

  • Original 153.9 kB
  • After minification 153.9 kB
  • After compression 152.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 850 B

  • Original 41.0 kB
  • After minification 41.0 kB
  • After compression 40.2 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. Slayer.film has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (65%)

Requests Now

31

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

slayer.film

slayer.film

13 ms

www.slayer.film

www.slayer.film

17 ms

www.slayer.film

www.slayer.film

129 ms

showtimes.css

showtimes.css

105 ms

css

css

30 ms

raven.min.js

raven.min.js

23 ms

showtimes.js

showtimes.js

177 ms

facebook.png

facebook.png

37 ms

twitter2.png

twitter2.png

17 ms

whatsapp.png

whatsapp.png

16 ms

title-short-bare.jpg

title-short-bare.jpg

219 ms

onesheet.jpg

onesheet.jpg

636 ms

legal-logos.png

legal-logos.png

16 ms

showtimes_bg.jpg

showtimes_bg.jpg

19 ms

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

24 ms

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

218 ms

geo

geo

307 ms

gtm.js

gtm.js

136 ms

fbevents.js

fbevents.js

38 ms

tracker.js

tracker.js

219 ms

embed.js

embed.js

85 ms

sign

sign

350 ms

238908603183726

238908603183726

90 ms

8132

8132

125 ms

destination

destination

37 ms

uwt.js

uwt.js

73 ms

events.js

events.js

86 ms

153628082142612

153628082142612

73 ms

landing

landing

78 ms

screenings

screenings

111 ms

69 ms

adsct

adsct

135 ms

adsct

adsct

136 ms

main.MTNhZGZiOTRkMA.js

main.MTNhZGZiOTRkMA.js

33 ms

1471628853145163

1471628853145163

55 ms

landing

landing

69 ms

32 ms

iframe_api

iframe_api

63 ms

www-widgetapi.js

www-widgetapi.js

8 ms

Accessibility Review

slayer.film accessibility score

83

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

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

Some elements have a [tabindex] value greater than 0

Best Practices

slayer.film best practices score

67

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

slayer.film SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slayer.film 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 Slayer.film 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

slayer.film

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