Tools & Wizards About Us
escire.net screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

escire.net

Ciencia Abierta | EScire

Page Load Speed

3 sec in total

First Response

401 ms

Resources Loaded

2.3 sec

Page Rendered

277 ms

escire.net screenshot

About Website

Click here to check amazing EScire content for Mexico. Otherwise, check out these important facts you probably never knew about escire.net

Ciencia Abierta, proyectos de DSpace, OJS, y gestión digital de la información. eScire es una empresa consultora enfocada al acceso abierto.

Visit escire.net

Key Findings

We analyzed Escire.net page load time and found that the first response time was 401 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

escire.net performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value1,840 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

escire.mx

401 ms

wp-emoji-release.min.js

167 ms

font-awesome.min.css

167 ms

shortcodes.css

114 ms

style.css

332 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Escire.net, 31% (19 requests) were made to Static.xx.fbcdn.net and 13% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Staticxx.facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 319.4 kB (55%)

Content Size

578.7 kB

After Optimization

259.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Escire.net main page is 578.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. 55% of websites need less resources to load. CSS take 207.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 16.2 kB

  • Original 22.6 kB
  • After minification 21.8 kB
  • After compression 6.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. 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 16.2 kB or 72% of the original size.

Image Optimization

-4%

Potential reduce by 6.4 kB

  • Original 171.9 kB
  • After minification 165.5 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. EScire images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 121.6 kB

  • Original 176.3 kB
  • After minification 174.4 kB
  • After compression 54.7 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 121.6 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 175.1 kB

  • Original 207.9 kB
  • After minification 169.0 kB
  • After compression 32.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. Escire.net needs all CSS files to be minified and compressed as it can save up to 175.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (49%)

Requests Now

59

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EScire. 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 from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

escire.mx

escire.mx

401 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

167 ms

font-awesome.min.css

font-awesome.min.css

167 ms

shortcodes.css

shortcodes.css

114 ms

style.css

style.css

332 ms

css

css

25 ms

font-awesome.css

font-awesome.css

177 ms

jquery.js

jquery.js

282 ms

jquery-migrate.min.js

jquery-migrate.min.js

167 ms

jscripts.php

jscripts.php

206 ms

shortcodes.js

shortcodes.js

171 ms

bootstrap.min.js

bootstrap.min.js

173 ms

theme.js

theme.js

182 ms

jscripts-ftr-min.js

jscripts-ftr-min.js

210 ms

wp-embed.min.js

wp-embed.min.js

228 ms

eScire.jpg

eScire.jpg

135 ms

icono3.png

icono3.png

136 ms

icono1-1.png

icono1-1.png

139 ms

icono4.png

icono4.png

136 ms

icono2-1.png

icono2-1.png

136 ms

dspace.jpg

dspace.jpg

137 ms

koha.jpg

koha.jpg

137 ms

ojs.jpg

ojs.jpg

138 ms

sdk.js

sdk.js

104 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

155 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

183 ms

114 ms

shortcodes-tablet.css

shortcodes-tablet.css

58 ms

shortcodes-mobile.css

shortcodes-mobile.css

57 ms

xd_arbiter.php

xd_arbiter.php

1010 ms

xd_arbiter.php

xd_arbiter.php

32 ms

page.php

page.php

264 ms

Xr6T9jq_7DM.css

Xr6T9jq_7DM.css

33 ms

lnL0YI3IxWI.css

lnL0YI3IxWI.css

40 ms

fG0y3ka9ETY.css

fG0y3ka9ETY.css

38 ms

gevUuEH7cch.css

gevUuEH7cch.css

35 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

45 ms

YvxwM8R7ol8.js

YvxwM8R7ol8.js

59 ms

ihptErjAmMX.js

ihptErjAmMX.js

65 ms

3So47A9WcrL.js

3So47A9WcrL.js

69 ms

cUsKAwzqrQw.js

cUsKAwzqrQw.js

70 ms

10941024_786612631415080_9193717697701234759_n.jpg

10941024_786612631415080_9193717697701234759_n.jpg

106 ms

safe_image.php

safe_image.php

104 ms

lRyN50VcaFW.js

lRyN50VcaFW.js

26 ms

safe_image.php

safe_image.php

43 ms

safe_image.php

safe_image.php

636 ms

539071_452889208120759_911547555_n.jpg

539071_452889208120759_911547555_n.jpg

27 ms

269936_613948381963186_1227921932_n.jpg

269936_613948381963186_1227921932_n.jpg

40 ms

12814545_991136054256520_3894080632047080544_n.jpg

12814545_991136054256520_3894080632047080544_n.jpg

40 ms

12341542_10205434536078570_4023625319408197390_n.jpg

12341542_10205434536078570_4023625319408197390_n.jpg

39 ms

1272_10153165981021954_3758154530451363690_n.jpg

1272_10153165981021954_3758154530451363690_n.jpg

40 ms

12670853_1093901580628548_1344216415988835210_n.jpg

12670853_1093901580628548_1344216415988835210_n.jpg

40 ms

582017_385422821490855_401561483_n.jpg

582017_385422821490855_401561483_n.jpg

80 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

18 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

19 ms

bNvHN6v1NeH.png

bNvHN6v1NeH.png

24 ms

b53Ajb4ihCP.gif

b53Ajb4ihCP.gif

24 ms

GtIpNnEyqq_.png

GtIpNnEyqq_.png

19 ms

R9a_DtVRZgv.js

R9a_DtVRZgv.js

4 ms

cUDgRFxaoIk.js

cUDgRFxaoIk.js

5 ms

0JBr1QHp8Gi.js

0JBr1QHp8Gi.js

5 ms

kDOzhTr2W91.js

kDOzhTr2W91.js

7 ms

Accessibility Review

escire.net accessibility score

76

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

escire.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

escire.net SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Escire.net 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 Escire.net 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.

Social Sharing Optimization

escire.net

Open Graph description is not detected on the main page of EScire. 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: