Tools & Wizards About Us
worth.es screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

worth.es

El Tiempo

Page Load Speed

3.4 sec in total

First Response

363 ms

Resources Loaded

2.5 sec

Page Rendered

469 ms

worth.es screenshot

About Website

Visit worth.es now to see the best up-to-date Worth content and also check out these interesting facts you probably never knew about worth.es

El Tiempo de hoy en España y el mundo. Previsión del tiempo para hoy, mañana y los próximos días. El Tiempo en 200.000 ciudades.

Visit worth.es

Key Findings

We analyzed Worth.es page load time and found that the first response time was 363 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

worth.es performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value2,490 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.151

75/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

worth.es

363 ms

site.css

217 ms

ga.js

17 ms

fondo.jpg

629 ms

logo.png

233 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 95% of them (39 requests) were addressed to the original Worth.es, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Worth.es.

Page Optimization Overview & Recommendations

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

Content Size

708.9 kB

After Optimization

660.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 18.6 kB

  • Original 22.0 kB
  • After minification 13.0 kB
  • After compression 3.4 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. This page needs HTML code to be minified as it can gain 9.0 kB, which is 41% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 18.6 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 26.5 kB

  • Original 665.6 kB
  • After minification 639.1 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. Worth images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-78%

Potential reduce by 3.3 kB

  • Original 4.2 kB
  • After minification 3.3 kB
  • After compression 900 B

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. Worth.es needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

40

After Optimization

40

  • Images
  • JavaScript
  • CSS

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Worth. According to our analytics all requests are already optimized.

Network Requests Diagram

worth.es

worth.es

363 ms

site.css

site.css

217 ms

ga.js

ga.js

17 ms

fondo.jpg

fondo.jpg

629 ms

logo.png

logo.png

233 ms

home1.png

home1.png

225 ms

quienes1.png

quienes1.png

232 ms

nuestro1.png

nuestro1.png

225 ms

clientes1.png

clientes1.png

234 ms

proyectos1.png

proyectos1.png

430 ms

unete1.png

unete1.png

443 ms

contacto1.png

contacto1.png

438 ms

destacado_superior.png

destacado_superior.png

1038 ms

botonhome.png

botonhome.png

467 ms

lineas_central.png

lineas_central.png

643 ms

central_op1.png

central_op1.png

671 ms

gestion.png

gestion.png

682 ms

central2_op1.png

central2_op1.png

703 ms

desarrollo.png

desarrollo.png

839 ms

central3_op1.png

central3_op1.png

858 ms

diseno.png

diseno.png

881 ms

fondo_centro.gif

fondo_centro.gif

910 ms

destacados.png

destacados.png

1131 ms

destacado3.png

destacado3.png

1309 ms

destacado2.png

destacado2.png

1406 ms

destacado1.png

destacado1.png

1472 ms

botondest1.png

botondest1.png

1158 ms

botondest2.png

botondest2.png

1256 ms

botondest3.png

botondest3.png

1342 ms

fondopx.jpg

fondopx.jpg

1383 ms

__utm.gif

__utm.gif

17 ms

home2.png

home2.png

118 ms

quienes2.png

quienes2.png

213 ms

nuestro2.png

nuestro2.png

232 ms

clientes2.png

clientes2.png

241 ms

proyectos2.png

proyectos2.png

238 ms

unete2.png

unete2.png

237 ms

contacto2.png

contacto2.png

342 ms

central_op2.png

central_op2.png

435 ms

central2_op2.png

central2_op2.png

436 ms

central3_op2.png

central3_op2.png

447 ms

Accessibility Review

worth.es accessibility score

63

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

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

worth.es 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

High

Page has valid source maps

SEO Factors

worth.es 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

    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 Worth.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 Worth.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

worth.es

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