Tools & Wizards About Us
cinemasie.com screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

cinemasie.com

Cinemasie: the database

Page Load Speed

2.7 sec in total

First Response

273 ms

Resources Loaded

2.3 sec

Page Rendered

105 ms

cinemasie.com screenshot

About Website

Click here to check amazing Cinemasie content for Serbia. Otherwise, check out these important facts you probably never knew about cinemasie.com

Visit cinemasie.com

Key Findings

We analyzed Cinemasie.com page load time and found that the first response time was 273 ms and then it took 2.4 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

cinemasie.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

cinemasie.com

273 ms

471 ms

base2tactu.css

163 ms

css2_pres.css

168 ms

prototype.js

462 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 88% of them (21 requests) were addressed to the original Cinemasie.com, 8% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to M1.nedstatbasic.net. The less responsive or slowest element that took the longest time to load (590 ms) relates to the external source M1.nedstatbasic.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 229.9 kB (76%)

Content Size

301.5 kB

After Optimization

71.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cinemasie.com main page is 301.5 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. 15% of websites need less resources to load. Javascripts take 258.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 19.8 kB

  • Original 25.4 kB
  • After minification 23.5 kB
  • After compression 5.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 19.8 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 80 B

  • Original 1.1 kB
  • After minification 1.0 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. Cinemasie images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 196.8 kB

  • Original 258.8 kB
  • After minification 193.8 kB
  • After compression 62.0 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 196.8 kB or 76% of the original size.

CSS Optimization

-81%

Potential reduce by 13.2 kB

  • Original 16.2 kB
  • After minification 9.1 kB
  • After compression 3.0 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. Cinemasie.com needs all CSS files to be minified and compressed as it can save up to 13.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (77%)

Requests Now

22

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cinemasie.com

cinemasie.com

273 ms

471 ms

base2tactu.css

base2tactu.css

163 ms

css2_pres.css

css2_pres.css

168 ms

prototype.js

prototype.js

462 ms

livesearch.js

livesearch.js

183 ms

scriptaculous.js

scriptaculous.js

194 ms

base-hactu.css

base-hactu.css

85 ms

base-g.css

base-g.css

97 ms

builder.js

builder.js

85 ms

effects.js

effects.js

193 ms

dragdrop.js

dragdrop.js

192 ms

controls.js

controls.js

252 ms

n

n

590 ms

wait.gif

wait.gif

85 ms

cinemasie_actu.gif

cinemasie_actu.gif

95 ms

fr_actu_non.gif

fr_actu_non.gif

96 ms

en_actu_non.gif

en_actu_non.gif

84 ms

search.png

search.png

93 ms

fond_transp.png

fond_transp.png

93 ms

fleche.png

fleche.png

166 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

11 ms

css2_pres.handheld.css

css2_pres.handheld.css

85 ms

Accessibility Review

cinemasie.com accessibility score

66

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

cinemasie.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

cinemasie.com SEO score

62

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cinemasie.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Cinemasie.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

cinemasie.com

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