5 sec in total
246 ms
4.2 sec
525 ms
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.esWe analyzed Infoexpres.es page load time and found that the first response time was 246 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
infoexpres.es performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value7.6 s
4/100
25%
Value10.7 s
7/100
10%
Value90 ms
99/100
30%
Value0.002
100/100
15%
Value11.8 s
17/100
10%
246 ms
169 ms
582 ms
159 ms
161 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Infoexpres.es, 59% (70 requests) were made to Teleelx.es and 21% (25 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Teleelx.es.
Page size can be reduced by 546.3 kB (17%)
3.2 MB
2.6 MB
In fact, the total size of Infoexpres.es main page is 3.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. 70% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 27.0 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 27.0 kB or 74% of the original size.
Potential reduce by 21.6 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. Infoexpres images are well optimized though.
Potential reduce by 240.9 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 240.9 kB or 65% of the original size.
Potential reduce by 256.8 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. Infoexpres.es needs all CSS files to be minified and compressed as it can save up to 256.8 kB or 83% of the original size.
Number of requests can be reduced by 21 (18%)
114
93
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Infoexpres. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
infoexpres.es
246 ms
www.infoexpres.es
169 ms
www.teleelx.es
582 ms
estilos.css
159 ms
elecciones.css
161 ms
jquery.min.js
550 ms
funciones.js
162 ms
swfobject.js
242 ms
slimbox.js
310 ms
banner-popup.css
311 ms
layout.css
155 ms
header.css
387 ms
slimbox.css
255 ms
analytics.js
26 ms
adj_56b8666b3b86d.gif
1704 ms
facebook_gris.png
112 ms
twitter_gris.png
205 ms
youtube_gris.png
204 ms
rss_gris.png
203 ms
tele_elx.png
275 ms
11n.gif
274 ms
tele_teleelx.png
404 ms
radio_elx.png
403 ms
app_teleelx.png
403 ms
adj_56896ec4e9c12.gif
868 ms
empleo.jpg
640 ms
club-amigos.gif
726 ms
adj_5410366849dad.gif
1055 ms
loterias.png
598 ms
horarios.png
733 ms
mercadillo.png
803 ms
cartelera.png
901 ms
farmacias.png
903 ms
blog.png
980 ms
adj_5613977237067.jpg
1179 ms
t_tele_elx.png
1056 ms
skyline.png
1038 ms
lupa.gif
1115 ms
adj-56e95d04c1117-244904-650-1800.JPG
1568 ms
mascara.png
1195 ms
bocadillo1.png
1198 ms
adj-56e95238ce6ed-390656-415-900.jpg
1430 ms
bocadillo2.png
1326 ms
adj-56e961e15b216-111417-300-900.jpg
1499 ms
adj-56e9601f83479-104648-300-900.jpg
1500 ms
adj-56e967888e990-162305-415-900.jpg
1675 ms
adj-56e95f760d89c-44860-415-900.jpg
1753 ms
adj-56e9617499129-72882-300-900.jpg
1748 ms
adj-56e963a8b4b05-120583-300-900.jpg
1750 ms
adj-56e966c89faec-602913-300-900.jpg
1827 ms
collect
32 ms
5G0qw62OsXI
106 ms
widgets.js
28 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
31 ms
adj-56e966e7c81ab-87649-300-900.jpg
1822 ms
syndication
105 ms
364722327218425856
151 ms
www-embed-player-vflRGs1ko.css
70 ms
www-embed-player.js
92 ms
base.js
156 ms
adj-56e9205b07414-176617-300-900.jpg
1828 ms
adj-5423d0c6a6136-9009-198-250.jpg
1729 ms
play.png
1728 ms
adj-56c59809728f6-11830-198-250.jpg
1659 ms
adj-56d58fc4bd72f-7104-198-250.jpg
1733 ms
proxy.jpg
238 ms
proxy.jpg
193 ms
proxy.jpg
150 ms
proxy.jpg
287 ms
proxy.jpg
225 ms
proxy.jpg
166 ms
proxy.jpg
242 ms
proxy.jpg
269 ms
proxy.jpg
279 ms
proxy.jpg
281 ms
proxy.jpg
279 ms
proxy.jpg
283 ms
proxy.jpg
281 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
112 ms
ad_status.js
92 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
15 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
12 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
160 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
161 ms
adj-56e7e7072a5c5-269073-198-250.jpg
1768 ms
adj-564aff54620db-48407-198-250.jpg
1768 ms
adj-56cdb6c2e8946-165810-198-250.jpg
1769 ms
i27TQxCu_normal.jpeg
91 ms
Mv4fgDci_normal.jpg
89 ms
Cdq1zz-WAAAr3KK.jpg:small
123 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
112 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
124 ms
proxy.jpg
53 ms
adj-56e957d7370e0-70189-340-500.jpg
1653 ms
proxy.jpg
47 ms
proxy.jpg
51 ms
proxy.jpg
216 ms
adj-56e2ffa4ba43b-54698-340-500.jpg
1611 ms
proxy.jpg
34 ms
proxy.jpg
53 ms
proxy.jpg
26 ms
proxy.jpg
44 ms
proxy.jpg
40 ms
adj-56e961e15b216-111417-340-500.jpg
1625 ms
proxy.jpg
52 ms
adj-56e96988dab45-65092-500-500.jpg
1739 ms
proxy.jpg
44 ms
proxy.jpg
49 ms
adj-56c37beb4d6b3-165764-325-1000.jpg
1676 ms
trans-negro.png
1462 ms
adj-56e947288cfed-998638-325-1000.png
1973 ms
adj-567a7e618df3d-640717-300-500.jpg
1582 ms
adj-56e44a4eba227-91975-300-500.jpg
1727 ms
adj-56963efce7e7a-197429-300-500.jpg
1524 ms
adjuntos_fichero_01cead66e46001ea-5392-300-500.jpg
1572 ms
adj-56e96b318dc1d-482005-300-500.jpg
1726 ms
fnd-gris.gif
1510 ms
cancel.png
1552 ms
jot.html
2 ms
infoexpres.es accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
infoexpres.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
infoexpres.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
ES
ES
ISO-8859-1
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 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.
infoexpres.es
Open Graph description is not detected on the main page of Infoexpres. 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: