Tools & Wizards About Us
cinemaware.eu screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

cinemaware.eu

Softvér na predaj vstupeniek v pokladni, online - Ticketware

Page Load Speed

3.7 sec in total

First Response

377 ms

Resources Loaded

2.9 sec

Page Rendered

336 ms

cinemaware.eu screenshot

About Website

Click here to check amazing Cinemaware content for Slovakia. Otherwise, check out these important facts you probably never knew about cinemaware.eu

Komplexné riešenie na predaj vstupeniek a online marketing. Pre kiná, kultúrne centrá a divadlá. Predávajte vstupenky moderným a inovatívnym spôsobom.

Visit cinemaware.eu

Key Findings

We analyzed Cinemaware.eu page load time and found that the first response time was 377 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 60% of websites can load faster.

Performance Metrics

cinemaware.eu performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value18.5 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

cinemaware.eu

377 ms

www.ticketware.sk

485 ms

www.ticketware.sk

427 ms

autoptimize_c7eec1335826d2b59d9547c6685d5dbd.css

91 ms

style.min.css

282 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Cinemaware.eu, 71% (39 requests) were made to Ticketware.sk and 13% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (844 ms) relates to the external source Ticketware.sk.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.0 kB (2%)

Content Size

1.4 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cinemaware.eu main page is 1.4 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 31.1 kB

  • Original 41.7 kB
  • After minification 41.7 kB
  • After compression 10.6 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 31.1 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 50 B

  • Original 1.0 MB
  • After minification 1.0 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. Cinemaware images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 287.0 kB
  • After minification 287.0 kB
  • After compression 284.2 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

-0%

Potential reduce by 72 B

  • Original 49.4 kB
  • After minification 49.4 kB
  • After compression 49.4 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. Cinemaware.eu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (35%)

Requests Now

43

After Optimization

28

  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cinemaware. 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

cinemaware.eu

cinemaware.eu

377 ms

www.ticketware.sk

www.ticketware.sk

485 ms

www.ticketware.sk

www.ticketware.sk

427 ms

autoptimize_c7eec1335826d2b59d9547c6685d5dbd.css

autoptimize_c7eec1335826d2b59d9547c6685d5dbd.css

91 ms

style.min.css

style.min.css

282 ms

application.combined.js

application.combined.js

455 ms

js

js

60 ms

css

css

42 ms

jquery.countTo.min.js

jquery.countTo.min.js

302 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

303 ms

jquery.appear.min.js

jquery.appear.min.js

303 ms

wow.min.js

wow.min.js

304 ms

scripts.js

scripts.js

369 ms

retina.min.js

retina.min.js

375 ms

scripts.js

scripts.js

377 ms

jquery.fancybox.js

jquery.fancybox.js

380 ms

api.js

api.js

51 ms

wp-embed.min.js

wp-embed.min.js

382 ms

web.js

web.js

55 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

117 ms

logo.png

logo.png

116 ms

distribucia-vstupeniek2.png

distribucia-vstupeniek2.png

309 ms

home-infografika.png

home-infografika.png

406 ms

fotky1.jpg

fotky1.jpg

114 ms

fotky2.jpg

fotky2.jpg

115 ms

fotky3.jpg

fotky3.jpg

230 ms

fotky4.jpg

fotky4.jpg

229 ms

fotky11.jpg

fotky11.jpg

229 ms

fotky16.jpg

fotky16.jpg

229 ms

fotky12.jpg

fotky12.jpg

305 ms

fotky13.jpg

fotky13.jpg

311 ms

fotky14.jpg

fotky14.jpg

305 ms

fotky15.jpg

fotky15.jpg

309 ms

fotky6.jpg

fotky6.jpg

393 ms

fotky7.jpg

fotky7.jpg

394 ms

fotky8.jpg

fotky8.jpg

402 ms

fotky9.jpg

fotky9.jpg

403 ms

fotky10.jpg

fotky10.jpg

404 ms

ticketware-long.svg

ticketware-long.svg

480 ms

sdk.js

sdk.js

94 ms

cover-home2.png

cover-home2.png

728 ms

sprite.png

sprite.png

472 ms

home-referencie2.png

home-referencie2.png

844 ms

footer-icoPray.png

footer-icoPray.png

450 ms

recaptcha__en.js

recaptcha__en.js

67 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

96 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

111 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

122 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

125 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

135 ms

z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuvMQQ.woff

z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuvMQQ.woff

135 ms

z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuvMQQ.woff

z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuvMQQ.woff

250 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

480 ms

sdk.js

sdk.js

12 ms

83 ms

Accessibility Review

cinemaware.eu accessibility score

55

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

cinemaware.eu best practices score

75

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

SEO Factors

cinemaware.eu SEO score

85

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

    SK

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

cinemaware.eu

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