Tools & Wizards About Us
cronologic.es screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 0

    Best Practices

  • 86

    SEO

    Google-friendlier than
    60% of websites

cronologic.es

Page Load Speed

2 sec in total

First Response

225 ms

Resources Loaded

1.6 sec

Page Rendered

184 ms

cronologic.es screenshot

About Website

Welcome to cronologic.es homepage info - get ready to check Cronologic best content for Spain right away, or after learning these important things about cronologic.es

Viaja en el tiempo ⌛ ¡Reserva tu Escape Room en Barcelona de Ciencia-Ficción! 4º Premio a Mejor Marca Nacional de 2022 ✨

Visit cronologic.es

Key Findings

We analyzed Cronologic.es page load time and found that the first response time was 225 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

cronologic.es performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value21.9 s

0/100

25%

SI (Speed Index)

Value20.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,300 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value24.1 s

0/100

10%

Network Requests Diagram

cronologic.es

225 ms

142 ms

estils.css

115 ms

sbimenu.css

181 ms

css

24 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 80% of them (20 requests) were addressed to the original Cronologic.es, 8% (2 requests) were made to Fonts.googleapis.com and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (721 ms) belongs to the original domain Cronologic.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 368.6 kB (31%)

Content Size

1.2 MB

After Optimization

815.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cronologic.es main page is 1.2 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. 20% of websites need less resources to load. Images take 684.3 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 3.8 kB

  • Original 5.7 kB
  • After minification 5.4 kB
  • After compression 1.9 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 3.8 kB or 67% of the original size.

Image Optimization

-1%

Potential reduce by 6.8 kB

  • Original 684.3 kB
  • After minification 677.5 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. Cronologic images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 326.8 kB

  • Original 455.1 kB
  • After minification 453.4 kB
  • After compression 128.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 326.8 kB or 72% of the original size.

CSS Optimization

-79%

Potential reduce by 31.1 kB

  • Original 39.2 kB
  • After minification 36.1 kB
  • After compression 8.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. Cronologic.es needs all CSS files to be minified and compressed as it can save up to 31.1 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (45%)

Requests Now

22

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cronologic.es

cronologic.es

225 ms

142 ms

estils.css

estils.css

115 ms

sbimenu.css

sbimenu.css

181 ms

css

css

24 ms

css

css

34 ms

calendar.css

calendar.css

260 ms

jquery_1.9.js

jquery_1.9.js

345 ms

jquery_ui.js

jquery_ui.js

438 ms

funcions.js

funcions.js

259 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

207 ms

jquery.bgImageMenu.js

jquery.bgImageMenu.js

674 ms

reset.css

reset.css

182 ms

UyYrYy3ltEffJV9QueSi4VLE0juxe_YrR4_5kH0wfhI.ttf

UyYrYy3ltEffJV9QueSi4VLE0juxe_YrR4_5kH0wfhI.ttf

10 ms

analytics.js

analytics.js

14 ms

silver.jpg

silver.jpg

721 ms

pxblanc.png

pxblanc.png

90 ms

visa-logo_s.jpg

visa-logo_s.jpg

342 ms

mastercard-logo.png

mastercard-logo.png

167 ms

collect

collect

21 ms

cargando.gif

cargando.gif

174 ms

cronologicP.jpg

cronologicP.jpg

320 ms

misionP.jpg

misionP.jpg

364 ms

reservasP.jpg

reservasP.jpg

321 ms

contactanosP.jpg

contactanosP.jpg

563 ms

Accessibility Review

cronologic.es accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

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.

SEO Factors

cronologic.es SEO score

86

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

Language and Encoding

  • Language Detected

    ES

  • 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 Cronologic.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Cronologic.es 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

cronologic.es

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