Tools & Wizards About Us
verjournal.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

verjournal.com

Vascular & Endovascular Review -

Page Load Speed

2.6 sec in total

First Response

374 ms

Resources Loaded

1.8 sec

Page Rendered

384 ms

verjournal.com screenshot

About Website

Visit verjournal.com now to see the best up-to-date Verjournal content and also check out these interesting facts you probably never knew about verjournal.com

Visit verjournal.com

Key Findings

We analyzed Verjournal.com page load time and found that the first response time was 374 ms and then it took 2.2 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

verjournal.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value18.1 s

0/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

verjournal.com

374 ms

frontend.min.css

120 ms

header-footer-elementor.css

130 ms

frontend-lite.min.css

135 ms

swiper.min.css

186 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 70% of them (44 requests) were addressed to the original Verjournal.com, 29% (18 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (666 ms) belongs to the original domain Verjournal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.9 kB (17%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Verjournal.com main page is 1.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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 119.6 kB

  • Original 143.4 kB
  • After minification 139.4 kB
  • After compression 23.8 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 119.6 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 34.2 kB

  • Original 1.2 MB
  • After minification 1.2 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. Verjournal images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 43.6 kB

  • Original 203.4 kB
  • After minification 203.4 kB
  • After compression 159.8 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 43.6 kB or 21% of the original size.

CSS Optimization

-61%

Potential reduce by 78.5 kB

  • Original 127.7 kB
  • After minification 127.4 kB
  • After compression 49.2 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. Verjournal.com needs all CSS files to be minified and compressed as it can save up to 78.5 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (77%)

Requests Now

44

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

verjournal.com

verjournal.com

374 ms

frontend.min.css

frontend.min.css

120 ms

header-footer-elementor.css

header-footer-elementor.css

130 ms

frontend-lite.min.css

frontend-lite.min.css

135 ms

swiper.min.css

swiper.min.css

186 ms

post-7.css

post-7.css

186 ms

frontend-lite.min.css

frontend-lite.min.css

190 ms

global.css

global.css

191 ms

post-138.css

post-138.css

194 ms

frontend.css

frontend.css

199 ms

post-108.css

post-108.css

250 ms

post-3819.css

post-3819.css

248 ms

css

css

34 ms

widget-icon-list.min.css

widget-icon-list.min.css

251 ms

widget-posts.min.css

widget-posts.min.css

250 ms

animations.min.css

animations.min.css

256 ms

frontend.min.js

frontend.min.js

313 ms

jquery.min.js

jquery.min.js

387 ms

jquery-migrate.min.js

jquery-migrate.min.js

315 ms

frontend.js

frontend.js

320 ms

imagesloaded.min.js

imagesloaded.min.js

319 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

320 ms

webpack.runtime.min.js

webpack.runtime.min.js

323 ms

frontend-modules.min.js

frontend-modules.min.js

431 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

405 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

406 ms

wp-polyfill.min.js

wp-polyfill.min.js

501 ms

hooks.min.js

hooks.min.js

418 ms

i18n.min.js

i18n.min.js

433 ms

frontend.min.js

frontend.min.js

441 ms

waypoints.min.js

waypoints.min.js

450 ms

core.min.js

core.min.js

451 ms

frontend.min.js

frontend.min.js

496 ms

elements-handlers.min.js

elements-handlers.min.js

526 ms

underscore.min.js

underscore.min.js

526 ms

wp-util.min.js

wp-util.min.js

534 ms

frontend.min.js

frontend.min.js

533 ms

Ver-Journal-logo.png

Ver-Journal-logo.png

556 ms

doah-icon.png

doah-icon.png

508 ms

Scopus-icon.png

Scopus-icon.png

444 ms

crossref-icon.png

crossref-icon.png

445 ms

vascular-rings.jpeg

vascular-rings.jpeg

465 ms

home-banner.jpg

home-banner.jpg

666 ms

sidebar-img.jpg

sidebar-img.jpg

479 ms

footer-bg01.jpg

footer-bg01.jpg

479 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

28 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

41 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

43 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

41 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

42 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

42 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

43 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

44 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

45 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

46 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

45 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0Uw.ttf

45 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf

46 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FV0Uw.ttf

66 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0Uw.ttf

69 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf

66 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf

68 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf

66 ms

Accessibility Review

verjournal.com accessibility score

97

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.

Best Practices

verjournal.com 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

verjournal.com SEO score

90

Search Engine Optimization Advices

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 Verjournal.com 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 Verjournal.com 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

verjournal.com

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