7.6 sec in total
274 ms
6.7 sec
637 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
Visit in.directe.catWe analyzed In.directe.cat page load time and found that the first response time was 274 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
in.directe.cat performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value28.1 s
0/100
25%
Value11.7 s
4/100
10%
Value2,840 ms
3/100
30%
Value0.022
100/100
15%
Value28.3 s
0/100
10%
274 ms
678 ms
39 ms
239 ms
246 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original In.directe.cat, 39% (55 requests) were made to Larepublica.cat and 22% (31 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 1.1 MB (40%)
2.7 MB
1.6 MB
In fact, the total size of In.directe.cat main page is 2.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 985.0 kB which makes up the majority of the site volume.
Potential reduce by 857.5 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 857.5 kB or 87% of the original size.
Potential reduce by 87.9 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 87.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 82.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 82.9 kB or 13% of the original size.
Potential reduce by 40.0 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 40.0 kB or 21% of the original size.
Number of requests can be reduced by 73 (70%)
104
31
The browser has sent 104 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 47 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
in.directe.cat
274 ms
www.larepublica.cat
678 ms
css
39 ms
frontend.min.css
239 ms
flatpickr.min.css
246 ms
select2.min.css
247 ms
yop-poll-public-6.5.30.css
338 ms
wpp.css
254 ms
style.css
257 ms
tds-front.css
318 ms
style.css
408 ms
style.css
329 ms
font-awesome.css
350 ms
td-multipurpose.css
353 ms
td_legacy_main.css
400 ms
td_standard_pack_main.css
577 ms
tdb_main.css
423 ms
jquery.min.js
508 ms
jquery-migrate.min.js
425 ms
flatpickr.min.js
480 ms
select2.min.js
489 ms
yop-poll-public-6.5.30.min.js
507 ms
wpp.min.js
510 ms
client.js
127 ms
js
59 ms
js
87 ms
la-republica_7358.js
125 ms
asyncjs.php
508 ms
adsbygoogle.js
105 ms
js
51 ms
frontend.min.js
407 ms
tagdiv_theme.min.js
419 ms
tdPostImages.js
456 ms
tdSmartSidebar.js
454 ms
tdSocialSharing.js
455 ms
tdModalPostImages.js
486 ms
comment-reply.min.js
499 ms
underscore.min.js
503 ms
js_files_for_front.min.js
528 ms
js_files_for_front.min.js
529 ms
tdLoadingBox.js
527 ms
tdInfiniteLoader.js
565 ms
tdbMenu.js
578 ms
tdToTop.js
583 ms
tdTrendingNow.js
610 ms
tdAjaxSearch.js
611 ms
tdbSearch.js
533 ms
hammer.min.js
559 ms
jquery.hammer.min.js
572 ms
widgets.css
495 ms
LOGO-LAREPUBLICA.png
138 ms
BCR-LOGO-400x400.png
140 ms
costa-400x400.png
380 ms
manzano-400x400.png
174 ms
la-republica-negatiu.png
140 ms
ajs.php
87 ms
analytics.js
222 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf
223 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rm.ttf
495 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSmb2Rm.ttf
495 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf
496 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf
498 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
498 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
498 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
498 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
498 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
500 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
499 ms
newspaper.woff
219 ms
7758d948c50dde6dd7a05312e970dc8a.gif
786 ms
lg.php
604 ms
va9B4kDNxMZdWfMOD5VnLK3eRhf_.ttf
382 ms
va9E4kDNxMZdWfMOD5Vvl4jO.ttf
381 ms
va9B4kDNxMZdWfMOD5VnPKreRhf_.ttf
384 ms
S6uyw4BMUTPHjx4wWw.ttf
271 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
274 ms
collect
175 ms
collect
167 ms
NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzZg.ttf
176 ms
NaPecZTIAOhVxoMyOr9n_E7fdMPmCA.ttf
175 ms
NaPDcZTIAOhVxoMyOr9n_E7ffBzCGItzZg.ttf
174 ms
neIQzD-0qpwxpaWvjeD0X88SAOeauXQ-pQ.ttf
176 ms
neIXzD-0qpwxpaWvjeD0X88SAOeasasatSyqwQ.ttf
175 ms
neIXzD-0qpwxpaWvjeD0X88SAOeasc8btSyqwQ.ttf
177 ms
neIXzD-0qpwxpaWvjeD0X88SAOeasfcZtSyqwQ.ttf
179 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
177 ms
cIfiMaFfvUQxTTqS3iKJkLGbI41wQL_vkBcr8zQ.ttf
178 ms
cIfiMaFfvUQxTTqS3iKJkLGbI41wQL86lxcr8zQ.ttf
178 ms
cIfiMaFfvUQxTTqS3iKJkLGbI41wQL8Ilxcr8zQ.ttf
179 ms
collect
202 ms
ga-audiences
184 ms
fontawesome-webfont.woff
175 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EICusdUmj.ttf
249 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSysdUmj.ttf
249 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yysdUmj.ttf
247 ms
d45b1fb6-5b5c-43a4-a234-bf942310c7ec-696x464.jpg
186 ms
f02e1da6-c199-41a1-82ce-22646aa59348-696x464.jpg
241 ms
1-111-e1650987842617.jpg
317 ms
1ae8de50-cafa-47cf-96f6-f8b2048563fd-696x464.jpg
316 ms
Imatge-Noti-1200x800-6-696x464.jpg
316 ms
3143316-1-696x464.jpg
389 ms
td-multipurpose.ttf
386 ms
show_ads_impl.js
245 ms
zrt_lookup.html
102 ms
ads
1300 ms
ads
1286 ms
ads
1212 ms
ca-pub-8738902543751983
270 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
118 ms
be.js
271 ms
asyncspc.php
149 ms
545 ms
B31835294.393145944;sz=300x600;ord=[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;dc_sdk_apis=[APIFRAMEWORKS];dc_omid_p=[OMIDPARTNER];gdpr=$%7BGDPR%7D;gdpr_consent=$%7BGDPR_CONSENT_755%7D;dc_tdv=1
129 ms
lg.php
99 ms
3ae40a2fa5d69b84aed39ff99e14ce5f.gif
278 ms
lg.php
278 ms
lg.php
433 ms
5f7dff7ddac37a22d6aa4e1c6d5d4b73.png
540 ms
lg.php
432 ms
lg.php
430 ms
d5d6b5959f80f6bf67a845043c58d895.gif
609 ms
lg.php
431 ms
lg.php
534 ms
lg.php
535 ms
c3po.jpg
211 ms
skeleton.js
163 ms
8953781499838780921
170 ms
sodar_loader.js
13 ms
ufs_web_display.js
38 ms
omrhp.js
154 ms
Q12zgMmT.js
173 ms
sodar
143 ms
ads
152 ms
ads
283 ms
main.19.8.504.js
107 ms
activeview
134 ms
62bHydCX.html
97 ms
sa30O7WeJNzu8x7oKdCcujxNj08-gvZudrea3FT7Uzc.js
9 ms
sodar2.js
57 ms
q3_ozqIbHCwHEmDedgzG-D6UnUyzi2L496FFdqoLokA.js
11 ms
in.directe.cat 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Page has valid source maps
in.directe.cat SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
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 does not match the claimed English 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: