18 sec in total
5 sec
11.3 sec
1.7 sec
Welcome to segre.com homepage info - get ready to check SEGRE best content for Spain right away, or after learning these important things about segre.com
Notícies d'última hora, actualitat, esports, política, imatges i vídeos i nous continguts formats. Lleida i comarques.
Visit segre.comWe analyzed Segre.com page load time and found that the first response time was 5 sec and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
segre.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value9.1 s
1/100
25%
Value10.4 s
8/100
10%
Value5,880 ms
0/100
30%
Value0.024
100/100
15%
Value26.9 s
0/100
10%
5003 ms
604 ms
17 ms
660 ms
736 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 10% of them (13 requests) were addressed to the original Segre.com, 70% (95 requests) were made to Imagenes.segre.com and 3% (4 requests) were made to Grup.segre.com. The less responsive or slowest element that took the longest time to load (5.3 sec) relates to the external source Grup.segre.com.
Page size can be reduced by 1.7 MB (16%)
10.3 MB
8.6 MB
In fact, the total size of Segre.com main page is 10.3 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. Only a small number of websites need less resources to load. Images take 9.3 MB which makes up the majority of the site volume.
Potential reduce by 388.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. This page needs HTML code to be minified as it can gain 91.8 kB, which is 20% 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 388.3 kB or 86% of the original size.
Potential reduce by 1.3 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. Obviously, SEGRE needs image optimization as it can save up to 1.3 MB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 189 B
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.
Potential reduce by 394 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. Segre.com has all CSS files already compressed.
Number of requests can be reduced by 19 (15%)
128
109
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SEGRE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
segre.com
5003 ms
www.segre.com
604 ms
screen.5c348ba9ab100f5a08b6.css
17 ms
render
660 ms
render
736 ms
firebase-app.js
42 ms
firebase-messaging.js
59 ms
prometeo-firebase.js
42 ms
home.bundle.js
29 ms
js
79 ms
loader.js
448 ms
loader.js
572 ms
desktop-mobile.min.js
136 ms
marfeel-sdk.es5.js
514 ms
css2
110 ms
gigya.js
345 ms
jquery.min.js
95 ms
663a4d81d8007.jpeg
1406 ms
portadaCAT.webp
5252 ms
6639a5829ee04.jpeg
1454 ms
64fd9d8fbe0d7.jpeg
1461 ms
663a0c417c597.jpeg
1460 ms
64f19b6ae8b66.jpeg
1459 ms
6639d6bbab437.jpeg
1462 ms
663a61429257f.png
1459 ms
6639a56e432d5.jpeg
1457 ms
64fc71d884b9d.jpeg
1462 ms
66370254d6f9e.r_d.600-400-0.jpeg
1462 ms
663740a10dba2.jpeg
1776 ms
6639cac14bb12.jpeg
1466 ms
6639d14a0854a.r_d.1616-1013-1753.jpeg
1465 ms
6639c6124c157.jpeg
1462 ms
65e6ce4348efc.jpeg
1464 ms
64f04c38d0408.png
1470 ms
6602f23611adc.jpeg
1465 ms
65088a4009c22.png
1466 ms
663a53a9b5c91.jpeg
1468 ms
66306acae9f4c.jpeg
1473 ms
66272fa946e52.png
1475 ms
652ff4c975ef7.jpeg
1473 ms
6628f326d7137.jpeg
1471 ms
6633b4c302904.jpeg
1474 ms
6631bba462a11.jpeg
1476 ms
6631bb68d03f6.jpeg
1478 ms
663a17c54613c.jpeg
1476 ms
663a1538986f5.jpeg
1478 ms
6619229f2deee.jpeg
1479 ms
64fb2000e7a24.jpeg
1478 ms
6639f5a0930a6.jpeg
1479 ms
64fd592794b21.jpeg
1482 ms
6636ff08349cc.jpeg
1481 ms
66248a4ac7563.png
1486 ms
663a5cce2b95b.jpeg
1482 ms
663a19a74571a.r_d.1651-1018-1378.jpeg
1745 ms
portadaCAT.webp
5236 ms
portadaSUP.webp
5239 ms
portadaSUP.webp
5239 ms
iconalink18.png
293 ms
20437307f8e1783ec0b2.svg
122 ms
font
276 ms
6c24f4a169ee7f2beba2.woff
334 ms
a3e66a3d0d26156cf2ca.woff
335 ms
4a463af37c9eaeca8205.woff
714 ms
font
272 ms
7747d036a5d751233216.woff
340 ms
player.instantvideocloud.net
257 ms
count.js
193 ms
lecturaportada.jpg
53 ms
xxiilogo.jpg
182 ms
lleidatvlogo.png
236 ms
prometeo-media.js
40 ms
beacon.js
34 ms
count-data.js
58 ms
ivc-player.js
68 ms
sdk.d8087c7a3cc56859060a6d91d2ce4afa58a9ec9c.js
55 ms
ui-gdpr-ca-web.d8087c7a3cc56859060a6d91d2ce4afa58a9ec9c.js
24 ms
663a19065e536.jpeg
369 ms
663a2c9fa4bb2.jpeg
280 ms
64f19b6ae8b66.jpeg
32 ms
6634f25e4e081.jpeg
35 ms
662f5ebc70449.jpeg
36 ms
662635642879b.jpeg
36 ms
66262f9de1941.jpeg
36 ms
6634b7f8f1f2d.png
37 ms
662f7338d319a.jpeg
37 ms
66224bc5f0b44.jpeg
38 ms
65000c8686e88.jpeg
35 ms
6639a4c66301c.jpeg
363 ms
6639a3547569d.jpeg
38 ms
6639a34096069.jpeg
41 ms
6639a32d10973.jpeg
44 ms
6638a99a00da7.jpeg
46 ms
6638a1ea8cd80.jpeg
61 ms
66388af17d8e8.jpeg
60 ms
663850369d8c8.jpeg
62 ms
64fd4e4a0e7f9.jpeg
68 ms
64fc7ac08055a.jpeg
71 ms
663a0f31ac8ee.jpeg
78 ms
6630f2403646c.jpeg
85 ms
6630daef09f84.jpeg
93 ms
663756cae39c5.jpeg
95 ms
6638a1ea8cd80.jpeg
101 ms
66330a5b27ed8.jpeg
108 ms
64f959505a55e.jpeg
113 ms
6633811560746.jpeg
115 ms
6639a22771116.jpeg
121 ms
6636ff204ea5d.jpeg
124 ms
6636ff0d3b391.jpeg
141 ms
663898a31050d.jpeg
142 ms
6636ff1e5307a.jpeg
143 ms
66248a35898b6.jpeg
145 ms
64ee0a528b8df.png
147 ms
662bd4a35bdc5.jpeg
148 ms
661ffa8d0741e.jpeg
418 ms
660450c45372b.jpeg
243 ms
65fc6b5b8c554.jpeg
249 ms
6638b5cbda0d2.jpeg
253 ms
662fda1d7325f.r_d.669-1655-1266.jpeg
261 ms
6627a94e44b1a.jpeg
257 ms
66264d26aa216.jpeg
270 ms
66190c040d264.jpeg
258 ms
660d11970889e.jpeg
278 ms
65c4bfb7ac099.jpeg
699 ms
6629cffea24e3.jpeg
247 ms
6639a1fef40be.jpeg
255 ms
662f15f5a3b67.jpeg
257 ms
65c64ac09b284.jpeg
255 ms
65c3b3a146625.jpeg
251 ms
65c22cee923db.r_d.626-611-0.jpeg
254 ms
663a61429257f.png
238 ms
663a5cce2b95b.jpeg
231 ms
663a53a9b5c91.jpeg
231 ms
663a4d81d8007.jpeg
226 ms
presidencia_blanc_h2.png
379 ms
premsa-comarca-eslogan-blanc.png
364 ms
segre.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
segre.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
segre.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
CA
![]()
CA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Segre.com can be misinterpreted by Google and other search engines. Our service has detected that Catalan is used on the page, and it matches the claimed language. Our system also found out that Segre.com 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.
segre.com
Open Graph data is detected on the main page of SEGRE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: