Tools & Wizards About Us
wjir.org screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

wjir.org

Home |WJIR | World Journal of Innovative Research | Publish paper in High Impact factor Engineering Medical Science Journal-wjir.org

Page Load Speed

2 sec in total

First Response

160 ms

Resources Loaded

1.6 sec

Page Rendered

221 ms

wjir.org screenshot

About Website

Visit wjir.org now to see the best up-to-date WJIR content for India and also check out these interesting facts you probably never knew about wjir.org

wjir.org: World Journal of Innovative Research is an international high impact peer reviewed open access engineering, science, technology, medical journal that publishes articles online and indexed in...

Visit wjir.org

Key Findings

We analyzed Wjir.org page load time and found that the first response time was 160 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wjir.org performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

wjir.org

160 ms

wjir.org

314 ms

main.css

268 ms

cbdb-search-form.css

278 ms

right_left_menu.css

285 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 89% of them (58 requests) were addressed to the original Wjir.org, 3% (2 requests) were made to Paypalobjects.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (511 ms) belongs to the original domain Wjir.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 172.8 kB (16%)

Content Size

1.1 MB

After Optimization

927.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wjir.org main page is 1.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. 35% of websites need less resources to load. Images take 908.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 38.3 kB

  • Original 48.0 kB
  • After minification 39.5 kB
  • After compression 9.7 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 8.5 kB, which is 18% 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 38.3 kB or 80% of the original size.

Image Optimization

-11%

Potential reduce by 102.1 kB

  • Original 908.7 kB
  • After minification 806.6 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. Obviously, WJIR needs image optimization as it can save up to 102.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 23.0 kB

  • Original 113.2 kB
  • After minification 113.1 kB
  • After compression 90.2 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 23.0 kB or 20% of the original size.

CSS Optimization

-31%

Potential reduce by 9.4 kB

  • Original 30.8 kB
  • After minification 30.8 kB
  • After compression 21.4 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. Wjir.org needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (45%)

Requests Now

58

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wjir.org

wjir.org

160 ms

wjir.org

wjir.org

314 ms

main.css

main.css

268 ms

cbdb-search-form.css

cbdb-search-form.css

278 ms

right_left_menu.css

right_left_menu.css

285 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

353 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

291 ms

twitter.js

twitter.js

293 ms

custom.js

custom.js

341 ms

style2.css

style2.css

343 ms

modernizr.custom.28468.js

modernizr.custom.28468.js

350 ms

jquery.cslider.js

jquery.cslider.js

355 ms

jquery.social.media.tabs.1.7.js

jquery.social.media.tabs.1.7.js

361 ms

tabs.js

tabs.js

403 ms

socal.css

socal.css

406 ms

jquery.validate.js

jquery.validate.js

422 ms

styles.css

styles.css

421 ms

jquery.complexify.js

jquery.complexify.js

428 ms

script.js

script.js

438 ms

jsDatePick_ltr.min.css

jsDatePick_ltr.min.css

467 ms

jsDatePick.min.1.3.js

jsDatePick.min.1.3.js

468 ms

js

js

87 ms

fonts.css

fonts.css

219 ms

web-style.css

web-style.css

222 ms

twitter.css

twitter.css

226 ms

transitions.css

transitions.css

238 ms

media.css

media.css

268 ms

prettyPhoto.css

prettyPhoto.css

267 ms

rss.png

rss.png

102 ms

46crossref-logo-200.png

46crossref-logo-200.png

368 ms

btn_paynowCC_LG.gif

btn_paynowCC_LG.gif

104 ms

header-bg.jpg

header-bg.jpg

293 ms

scrolltop.png

scrolltop.png

103 ms

settings.png

settings.png

101 ms

staffs.png

staffs.png

101 ms

logo20.png

logo20.png

133 ms

17axmb_logo.png

17axmb_logo.png

230 ms

9environment-icon-png-20.png

9environment-icon-png-20.png

241 ms

12marketing-png-1284.png

12marketing-png-1284.png

291 ms

11marketing-png-1308.png

11marketing-png-1308.png

357 ms

16phys_308px.png

16phys_308px.png

197 ms

arwblue.gif

arwblue.gif

266 ms

new.gif

new.gif

297 ms

download-icon.png

download-icon.png

311 ms

newbut.gif

newbut.gif

329 ms

32wjir_crossref_display.png

32wjir_crossref_display.png

511 ms

31neliti-blue.png

31neliti-blue.png

364 ms

25payumoney-payment-gateway.png

25payumoney-payment-gateway.png

374 ms

pixel.gif

pixel.gif

103 ms

analytics.js

analytics.js

109 ms

arrows.png

arrows.png

300 ms

nav.png

nav.png

315 ms

footer-bg.png

footer-bg.png

350 ms

google.png

google.png

361 ms

fblike.png

fblike.png

372 ms

twitter.png

twitter.png

384 ms

rss.png

rss.png

387 ms

loader.gif

loader.gif

412 ms

bg_white.png

bg_white.png

422 ms

controls.png

controls.png

442 ms

BebasNeue-webfont.woff

BebasNeue-webfont.woff

439 ms

Finalnew.ttf

Finalnew.ttf

442 ms

helveticaltstd-roman-webfont.woff

helveticaltstd-roman-webfont.woff

475 ms

collect

collect

13 ms

widgets.js

widgets.js

12 ms

Accessibility Review

wjir.org accessibility score

43

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

wjir.org best practices score

50

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

wjir.org SEO score

84

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wjir.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wjir.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

wjir.org

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