Tools & Wizards About Us
elm.jo screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    48% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

elm.jo

Electronic Library of Medicine - Jordan (ELM)::Powered by DeepKnowledge

Page Load Speed

3.6 sec in total

First Response

223 ms

Resources Loaded

3 sec

Page Rendered

424 ms

elm.jo screenshot

About Website

Visit elm.jo now to see the best up-to-date ELM content for Jordan and also check out these interesting facts you probably never knew about elm.jo

DeepKnowledge is an online platform that enables library end users to conduct searches on various subscriptions and online resources simultaneously and retrieve the results in a consistent and ranked ...

Visit elm.jo

Key Findings

We analyzed Elm.jo page load time and found that the first response time was 223 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

elm.jo performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.203

61/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

elm.jo

223 ms

index.aspx

57 ms

index

211 ms

js

124 ms

bootstrap.css

189 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 9% of them (7 requests) were addressed to the original Elm.jo, 44% (34 requests) were made to Staticfront.deepknowledge.io and 17% (13 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Bf5a0c8d48ca087745ff-5d297cdd9ffc2629bfe583fdf30af1c0.ssl.cf3.rackcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 513.9 kB (10%)

Content Size

5.3 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Elm.jo main page is 5.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. 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 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 262.6 kB

  • Original 337.1 kB
  • After minification 297.6 kB
  • After compression 74.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. This page needs HTML code to be minified as it can gain 39.5 kB, which is 12% 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 262.6 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 193.1 kB

  • Original 4.7 MB
  • After minification 4.5 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. ELM images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 47.0 kB

  • Original 159.0 kB
  • After minification 128.9 kB
  • After compression 112.0 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 47.0 kB or 30% of the original size.

CSS Optimization

-9%

Potential reduce by 11.2 kB

  • Original 120.8 kB
  • After minification 120.5 kB
  • After compression 109.6 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. Elm.jo has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 42 (63%)

Requests Now

67

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ELM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

elm.jo

elm.jo

223 ms

index.aspx

index.aspx

57 ms

index

index

211 ms

js

js

124 ms

bootstrap.css

bootstrap.css

189 ms

icons.min.css

icons.min.css

207 ms

select2.min.css

select2.min.css

205 ms

jquery-jvectormap-1.2.2.css

jquery-jvectormap-1.2.2.css

204 ms

switchery.min.css

switchery.min.css

178 ms

app.css

app.css

177 ms

flags16.css

flags16.css

231 ms

all.css

all.css

219 ms

jquery.scrolling-tabs.css

jquery.scrolling-tabs.css

225 ms

dk.css

dk.css

220 ms

vendor.min.js

vendor.min.js

224 ms

select2.min.js

select2.min.js

222 ms

jquery-jvectormap-1.2.2.min.js

jquery-jvectormap-1.2.2.min.js

226 ms

jquery-jvectormap-world-mill-en.js

jquery-jvectormap-world-mill-en.js

254 ms

switchery.min.js

switchery.min.js

225 ms

cssobj.iife.js

cssobj.iife.js

225 ms

icheck.min.js

icheck.min.js

225 ms

jquery.scrolling-tabs.js

jquery.scrolling-tabs.js

250 ms

app.js

app.js

260 ms

WebResource.axd

WebResource.axd

13 ms

analytics.js

analytics.js

116 ms

js

js

107 ms

css

css

279 ms

css

css

335 ms

_all.css

_all.css

45 ms

_all.css

_all.css

47 ms

_all.css

_all.css

43 ms

_all.css

_all.css

47 ms

polaris.css

polaris.css

45 ms

futurico.css

futurico.css

213 ms

collect

collect

42 ms

collect

collect

92 ms

b046c080-55ca-4f1d-bcca-2716e3929ae1.png

b046c080-55ca-4f1d-bcca-2716e3929ae1.png

1196 ms

google_play-512.png

google_play-512.png

347 ms

apple.svg

apple.svg

1266 ms

app-store.png

app-store.png

17 ms

google-play.png

google-play.png

16 ms

0ae6a213-bb23-4278-8c34-1752b84faa67.jpg

0ae6a213-bb23-4278-8c34-1752b84faa67.jpg

1414 ms

edb0e9e5-91cf-4a7e-acfe-93f704649de1.jpg

edb0e9e5-91cf-4a7e-acfe-93f704649de1.jpg

1409 ms

45b39f4a-71b5-4281-8140-6de7aed1af2a.jpg

45b39f4a-71b5-4281-8140-6de7aed1af2a.jpg

1414 ms

7a63f0aa-354c-4f0b-9060-d1e4a616b3c1.jpg

7a63f0aa-354c-4f0b-9060-d1e4a616b3c1.jpg

1413 ms

07bfc6e6-848f-4971-9849-0af228debaaf.png

07bfc6e6-848f-4971-9849-0af228debaaf.png

1412 ms

466b3318-073f-42c4-b232-389bcc0bfe7a.jpg

466b3318-073f-42c4-b232-389bcc0bfe7a.jpg

1514 ms

8fe46ea0-e5ff-4c27-a646-415d10048ec0.jpg

8fe46ea0-e5ff-4c27-a646-415d10048ec0.jpg

1515 ms

effd0d01-7a11-4eec-8716-ffc6bc780d38.jpg

effd0d01-7a11-4eec-8716-ffc6bc780d38.jpg

1516 ms

b6df952b-fe8c-4fe6-a09c-00c0944c01f4.png

b6df952b-fe8c-4fe6-a09c-00c0944c01f4.png

1513 ms

1a84d579-1b4a-4f54-aaec-fb5b0de6e794.png

1a84d579-1b4a-4f54-aaec-fb5b0de6e794.png

1504 ms

collect

collect

1248 ms

collect

collect

1258 ms

feather.woff

feather.woff

850 ms

materialdesignicons-webfont.woff

materialdesignicons-webfont.woff

985 ms

themify.woff

themify.woff

849 ms

fa-brands-400.woff

fa-brands-400.woff

918 ms

fa-solid-900.woff

fa-solid-900.woff

919 ms

fa-regular-400.woff

fa-regular-400.woff

849 ms

EDSCreateSession

EDSCreateSession

600 ms

GetGoogleAnalysis

GetGoogleAnalysis

425 ms

default

default

331 ms

grey.png

grey.png

87 ms

ga-audiences

ga-audiences

262 ms

GetEDSCriteria

GetEDSCriteria

173 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

86 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

91 ms

twk-event-polyfill.js

twk-event-polyfill.js

99 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

84 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

85 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

291 ms

twk-main.js

twk-main.js

95 ms

twk-vendor.js

twk-vendor.js

178 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

114 ms

twk-chunk-common.js

twk-chunk-common.js

99 ms

twk-runtime.js

twk-runtime.js

111 ms

twk-app.js

twk-app.js

114 ms

Accessibility Review

elm.jo accessibility score

93

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

Best Practices

elm.jo best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

elm.jo SEO score

73

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elm.jo can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Elm.jo 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

elm.jo

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