Tools & Wizards About Us
eajm.org screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

eajm.org

The Eurasian Journal of Medicine

Page Load Speed

3.5 sec in total

First Response

26 ms

Resources Loaded

3.3 sec

Page Rendered

187 ms

eajm.org screenshot

About Website

Welcome to eajm.org homepage info - get ready to check Eajm best content for Turkey right away, or after learning these important things about eajm.org

eajm

Visit eajm.org

Key Findings

We analyzed Eajm.org page load time and found that the first response time was 26 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

eajm.org performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value29.4 s

0/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

eajm.org

26 ms

eajm.org

288 ms

css

727 ms

js

64 ms

index.css

337 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 95% of them (37 requests) were addressed to the original Eajm.org, 3% (1 request) were made to Googletagmanager.com and 3% (1 request) were made to Js.trendmd.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Eajm.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 475.3 kB (27%)

Content Size

1.8 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eajm.org main page is 1.8 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. 30% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 25.8 kB

  • Original 31.8 kB
  • After minification 21.4 kB
  • After compression 5.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 10.4 kB, which is 33% 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 25.8 kB or 81% of the original size.

Image Optimization

-22%

Potential reduce by 318.5 kB

  • Original 1.4 MB
  • After minification 1.1 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. Obviously, Eajm needs image optimization as it can save up to 318.5 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-47%

Potential reduce by 126.3 kB

  • Original 270.6 kB
  • After minification 267.3 kB
  • After compression 144.3 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 126.3 kB or 47% of the original size.

CSS Optimization

-32%

Potential reduce by 4.6 kB

  • Original 14.5 kB
  • After minification 14.5 kB
  • After compression 9.9 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. Eajm.org needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (44%)

Requests Now

34

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eajm.org

eajm.org

26 ms

eajm.org

eajm.org

288 ms

css

css

727 ms

js

js

64 ms

index.css

index.css

337 ms

jquery-ui.css

jquery-ui.css

341 ms

modernizr-2.6.2.js

modernizr-2.6.2.js

339 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

364 ms

jquery.easings.min.js

jquery.easings.min.js

341 ms

bootstrap.min.js

bootstrap.min.js

671 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

875 ms

royal_preloader.min.js

royal_preloader.min.js

705 ms

layout.min.js

layout.min.js

689 ms

news_slider.min.js

news_slider.min.js

696 ms

left_slide.min.js

left_slide.min.js

1009 ms

_UI.min.js

_UI.min.js

1023 ms

index_slide.min.js

index_slide.min.js

1044 ms

jquery-ui.js

jquery-ui.js

1034 ms

AutoComp.min.js

AutoComp.min.js

1036 ms

trendmd.min.js

trendmd.min.js

46 ms

eajm.org

eajm.org

647 ms

aves-logo.png

aves-logo.png

579 ms

EAJM(1).png

EAJM(1).png

594 ms

%7BE00D0683-C3AB-44D9-A324-F4D07D307690%7D(2).png

%7BE00D0683-C3AB-44D9-A324-F4D07D307690%7D(2).png

602 ms

EAJM(4).png

EAJM(4).png

606 ms

EAJM(3).png

EAJM(3).png

617 ms

eajm(2).png

eajm(2).png

1804 ms

eajm3.png

eajm3.png

1811 ms

eajm5.png

eajm5.png

936 ms

eajm-e4.png

eajm-e4.png

978 ms

EAJM%20publons.jpg

EAJM%20publons.jpg

1856 ms

aves-logo-alt.png

aves-logo-alt.png

963 ms

yaysis.woff

yaysis.woff

1477 ms

montserrat-semibold-webfont.woff

montserrat-semibold-webfont.woff

1528 ms

yaysis-2.woff

yaysis-2.woff

1233 ms

_SearchFilter.min.js

_SearchFilter.min.js

1351 ms

CaptchaImg

CaptchaImg

167 ms

eajm.org

eajm.org

548 ms

123

123

173 ms

Accessibility Review

eajm.org accessibility score

64

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

eajm.org 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

Missing source maps for large first-party JavaScript

SEO Factors

eajm.org SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

eajm.org

Open Graph data is detected on the main page of Eajm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: