Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

infoexpres.es

Noticias de Elche en TeleElx: televisión local, radio, app y web

Page Load Speed

3.9 sec in total

First Response

195 ms

Resources Loaded

2.7 sec

Page Rendered

946 ms

About Website

Welcome to infoexpres.es homepage info - get ready to check Infoexpres best content right away, or after learning these important things about infoexpres.es

Noticias de última hora sobre la actualidad en Elche: política, economía, deportes, el tiempo, cultura, sociedad, tecnología, moda, ...

Visit infoexpres.es

Key Findings

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

Performance Metrics

infoexpres.es performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.391

26/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

infoexpres.es

195 ms

teleelx.es

435 ms

teleelx-elx_LOGO-2.png

79 ms

teleelx-elx_LOGO.png

122 ms

img-20240510-wa0008-400x240.jpg

200 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Infoexpres.es, 99% (78 requests) were made to Teleelx.es. The less responsive or slowest element that took the longest time to load (933 ms) relates to the external source Teleelx.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 196.7 kB (8%)

Content Size

2.4 MB

After Optimization

2.3 MB

In fact, the total size of Infoexpres.es main page is 2.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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 155.4 kB

  • Original 181.8 kB
  • After minification 181.1 kB
  • After compression 26.3 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 155.4 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 41.3 kB

  • Original 2.3 MB
  • After minification 2.2 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. Infoexpres images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

77

After Optimization

77

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

Accessibility Review

infoexpres.es accessibility score

85

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

infoexpres.es best practices score

75

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

infoexpres.es SEO score

84

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Infoexpres.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Infoexpres.es 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

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