11.1 sec in total
421 ms
9.6 sec
1.1 sec
Visit fedit.es now to see the best up-to-date FEDIT content and also check out these interesting facts you probably never knew about fedit.es
Visit fedit.esWe analyzed Fedit.es page load time and found that the first response time was 421 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fedit.es performance score
name
value
score
weighting
Value16.9 s
0/100
10%
Value43.1 s
0/100
25%
Value36.2 s
0/100
10%
Value8,110 ms
0/100
30%
Value0.12
84/100
15%
Value50.0 s
0/100
10%
421 ms
2799 ms
246 ms
690 ms
691 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fedit.es, 55% (88 requests) were made to Fedit.com and 12% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Fedit.com.
Page size can be reduced by 1.8 MB (44%)
4.1 MB
2.3 MB
In fact, the total size of Fedit.es main page is 4.1 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. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 264.2 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 264.2 kB or 87% of the original size.
Potential reduce by 36.4 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. FEDIT images are well optimized though.
Potential reduce by 783.6 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 783.6 kB or 72% of the original size.
Potential reduce by 758.3 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. Fedit.es needs all CSS files to be minified and compressed as it can save up to 758.3 kB or 85% of the original size.
Number of requests can be reduced by 84 (57%)
147
63
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEDIT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
fedit.es
421 ms
fedit.com
2799 ms
wp-emoji-release.min.js
246 ms
styles.css
690 ms
cli-style.css
691 ms
css
24 ms
style.css
1020 ms
settings.css
863 ms
css
35 ms
default.css
324 ms
css
52 ms
base.css
489 ms
layout.css
570 ms
style.css
901 ms
forums.css
843 ms
admin-ajax.php
2399 ms
responsive.css
1003 ms
css
48 ms
eventon_styles.css
1027 ms
font-awesome.css
950 ms
jquery.js
1060 ms
jquery-migrate.min.js
1031 ms
cookielawinfo.js
1081 ms
jquery.themepunch.tools.min.js
1185 ms
jquery.themepunch.revolution.min.js
1201 ms
eventon_dynamic_styles.css
252 ms
comment-reply.min.js
277 ms
jquery.form.min.js
298 ms
scripts.js
333 ms
idle-timer.min.js
358 ms
custom.js
379 ms
uwpqsfscript.js
402 ms
core.min.js
412 ms
widget.min.js
420 ms
tabs.min.js
437 ms
accordion.min.js
457 ms
jquery.transit.js
482 ms
jquery.selene.js
492 ms
jquery.quartz.js
503 ms
jquery.bxslider.js
518 ms
jquery.isotope.js
614 ms
jquery.prettyPhoto.js
564 ms
mediaelement-and-player.min.js
578 ms
wp-mediaelement.js
586 ms
idangerous.swiper-2.1.js
602 ms
idangerous.swiper.scrollbar-2.1.js
647 ms
ext.js
662 ms
custom.js
752 ms
wp-embed.min.js
683 ms
js
81 ms
eventon_functions.js
692 ms
_ioa_front.css
697 ms
jquery.mobile.min.js
663 ms
eventon_script.js
632 ms
eventon_gen_maps.js
625 ms
eventon_init_gmap.js
656 ms
logofedit_head.png
146 ms
dummy.png
147 ms
portada20141-320x220.jpg
147 ms
Portal1-320x220.jpg
269 ms
Centros-Fedit-320x220.jpg
145 ms
areas-02-300x213.png
145 ms
areas-01-300x213.png
269 ms
areas-04-300x213.png
1854 ms
areas-03-300x213.png
270 ms
matarromera-preformas-700x524.jpg
1875 ms
ImagenCongresoASLAN2016-700x525.jpg
1879 ms
Transfiere-2016-700x525.jpg
1880 ms
FEdit-Chile-700x525.jpg
1878 ms
IMG_0519-700x525.jpg
1878 ms
Foto-grupo-Colegio-Pod%C3%B3logos-Navarra-700x525.jpg
1879 ms
Cabecera-SEC016-700x525.jpg
2161 ms
I_HeERO-reuni%C3%B3n-11_11_2015_berlin-700x525.jpg
2241 ms
IMG_0031-700x525.jpg
2159 ms
MG_4294-700x525.jpg
2234 ms
150x150NuevoFormato.gif
2064 ms
EARTO.jpg
2180 ms
bannerIndustria40_250x250.png
2234 ms
banner_CON_borde.gif
2814 ms
portada2014.jpg
2796 ms
impacto1.jpg
2658 ms
comparativa1.jpg
2761 ms
carlos-50x50.jpg
2321 ms
sebastian-50x50.jpg
2321 ms
mayte-50x50.jpg
2654 ms
juan-50x50.jpg
2657 ms
jordi-50x50.jpg
2763 ms
carmen-50x50.jpg
2762 ms
logoearto.png
2762 ms
a3FuxozqUxY
137 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
73 ms
8KhZd3VQBtXTAznvKjw-ky3USBnSvpkopQaUR-2r7iU.ttf
75 ms
_ioa_front.woff
2952 ms
widgets.js
90 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
29 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
30 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
29 ms
overlay.png
2693 ms
www-embed-player-vflfNyN_r.css
1631 ms
www-embed-player.js
1679 ms
base.js
1744 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
57 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
57 ms
likebox.php
2028 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
308 ms
shadow3.png
965 ms
17123397358_4072f3af31_o.jpg
1299 ms
revicons.woff
1013 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
122 ms
ad_status.js
120 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
105 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
106 ms
syndication
181 ms
597378664507023360
502 ms
kyEKgjk51ZE.css
65 ms
xgj7bXhJNEH.css
70 ms
Czh0gDTFcBt.css
84 ms
N-k91nHCZS2.css
124 ms
ZeuPykSxSED.css
113 ms
q68gy-v_YMF.js
134 ms
FJmpeSpHpjS.js
159 ms
0wM5s1Khldu.js
112 ms
1bNoFZUdlYZ.js
88 ms
njO1TPvGzoR.js
182 ms
1QuX41zDRrx.js
182 ms
Oagsvfb4VWi.js
181 ms
LTv6ZK-5zxz.js
191 ms
1FCa-btixu2.js
190 ms
10172592_10153054090716531_3414194575439464373_n.jpg
272 ms
safe_image.php
264 ms
safe_image.php
251 ms
safe_image.php
297 ms
10312632_10153054090406531_4037385729288578227_n.png
278 ms
12733441_1047791198620415_7089555840384917238_n.jpg
296 ms
12744559_1047791268620408_6186413625865099346_n.jpg
327 ms
12717331_1047791345287067_6812343991301025220_n.jpg
326 ms
12715566_1047791435287058_2137713007807297866_n.jpg
327 ms
1475775_504517472980220_2034162294_n.png
326 ms
21299_487909184611339_146839927_n.png
327 ms
12670116_1327616353921002_145077287133957931_n.jpg
327 ms
12042709_747165265384159_9005569187236422150_n.png
340 ms
wL6VQj7Ab77.png
141 ms
s7jcwEQH7Sx.png
140 ms
QDwYpIaRyfG.png
140 ms
K00K-UgnsKu.png
139 ms
proxy.jpg
175 ms
proxy.jpg
178 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
90 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
84 ms
iq0h-7wk_normal.jpeg
268 ms
Mv4fgDci_normal.jpg
264 ms
3d0bb732fbd4c16eeb3b070843a85bf8_normal.png
301 ms
xiQQp7Ad_normal.png
332 ms
CIT_UPC_normal.png
367 ms
YQshazzh_normal.jpg
368 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
68 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
175 ms
I6-MnjEovm5.js
130 ms
pQrUxxo5oQp.js
130 ms
proxy.jpg
12 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
5 ms
fedit.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.
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
fedit.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fedit.es 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fedit.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 Fedit.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.
fedit.es
Open Graph description is not detected on the main page of FEDIT. 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: