7.9 sec in total
2.9 sec
4.6 sec
421 ms
Visit in.directe.cat now to see the best up-to-date In Directe content for Spain and also check out these interesting facts you probably never knew about in.directe.cat
Directe!cat, Informació amb independència
Visit in.directe.catWe analyzed In.directe.cat page load time and found that the first response time was 2.9 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
in.directe.cat performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value14.8 s
0/100
25%
Value23.8 s
0/100
10%
Value31,140 ms
0/100
30%
Value0.537
14/100
15%
Value55.0 s
0/100
10%
2893 ms
226 ms
234 ms
236 ms
251 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 56% of them (48 requests) were addressed to the original In.directe.cat, 19% (16 requests) were made to Ads.catmedia.cat and 6% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain In.directe.cat.
Page size can be reduced by 281.6 kB (52%)
545.7 kB
264.1 kB
In fact, the total size of In.directe.cat main page is 545.7 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. 40% of websites need less resources to load. Javascripts take 220.6 kB which makes up the majority of the site volume.
Potential reduce by 69.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. This page needs HTML code to be minified as it can gain 15.0 kB, which is 17% 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 69.9 kB or 78% of the original size.
Potential reduce by 76.0 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. Obviously, In Directe needs image optimization as it can save up to 76.0 kB or 39% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 101.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 101.9 kB or 46% of the original size.
Potential reduce by 33.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. In.directe.cat needs all CSS files to be minified and compressed as it can save up to 33.8 kB or 82% of the original size.
Number of requests can be reduced by 26 (31%)
84
58
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of In Directe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
in.directe.cat
2893 ms
continent.css
226 ms
estils.css
234 ms
formularis.css
236 ms
blog.estils.php
251 ms
jquery.js
374 ms
base.js
252 ms
plugins.js
340 ms
v60.js
64 ms
afr.php
637 ms
valora_over.png
120 ms
facebook_negre.png
124 ms
twitter_negre.png
115 ms
rss_negre.png
127 ms
directe.png
126 ms
logo.png
116 ms
enviar.png
225 ms
cerca.png
230 ms
rss_petit.png
237 ms
fletxa_negra.png
247 ms
josep-loste.jpg
251 ms
lectura.png
248 ms
comentari.png
336 ms
perfilindirecte_n.jpg
342 ms
xainegre_indirecte.jpg
353 ms
publicitat.png
368 ms
iniciativa-animalista.jpg
371 ms
logo-bloc-vermell.png
377 ms
xama.jpg
975 ms
gustaupixsel.gif
457 ms
fletxa_taronja.png
471 ms
2779
496 ms
3976
503 ms
3284
513 ms
documents.png
572 ms
publicitath.png
588 ms
logo_petit.png
618 ms
generalitat.jpg
628 ms
somerights20.png
694 ms
facebook.png
694 ms
twitter.png
705 ms
rss.png
738 ms
ajs.php
628 ms
f1124c232ab79c14def98dea26fffd73.gif
407 ms
lg.php
137 ms
afr.php
250 ms
afr.php
243 ms
afr.php
270 ms
afr.php
247 ms
7f0f255776ba98701c5207186b0f8ad5.gif
505 ms
lg.php
372 ms
opinador.png
133 ms
ajax.php
179 ms
loading.gif
120 ms
punter.png
130 ms
storageframe.html
23 ms
ga.js
29 ms
m
45 ms
__utm.gif
12 ms
__utm.gif
14 ms
fletxa_esquerra.png
151 ms
fletxa_dreta.png
151 ms
acte.png
151 ms
2d02bc87219042626b00e59257d87ab9.gif
549 ms
lg.php
143 ms
56435bb1450e36c1f7f29eae531f9219.gif
271 ms
lg.php
209 ms
adsbygoogle.js
5 ms
lg.php
245 ms
ca-pub-8738902543751983.js
34 ms
zrt_lookup.html
34 ms
show_ads_impl.js
58 ms
lg.php
226 ms
ads
352 ms
ads
282 ms
osd.js
9 ms
estils-print.css
129 ms
3630189462682736125
27 ms
abg.js
29 ms
m_js_controller.js
36 ms
googlelogo_color_112x36dp.png
82 ms
x_button_blue2.png
37 ms
s
34 ms
9343213784447188797
17 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
6 ms
in.directe.cat accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
in.directe.cat 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
Missing source maps for large first-party JavaScript
in.directe.cat 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 In.directe.cat 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 In.directe.cat 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.
in.directe.cat
Open Graph description is not detected on the main page of In Directe. 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: