Access wjrr.org. WJRR: High Impact Factor Journal| Research Paper Publication|Best International peer reviewed online...

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.112

87/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

wjrr.org

164 ms

wjrr.org

368 ms

main.css

254 ms

cbdb-search-form.css

274 ms

right_left_menu.css

278 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 81% of them (67 requests) were addressed to the original Wjrr.org, 5% (4 requests) were made to Gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (490 ms) belongs to the original domain Wjrr.org.

Content Size

1.1 MB

After Optimization

851.7 kB

In fact, the total size of Wjrr.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. 50% of websites need less resources to load. Images take 685.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 65.7 kB

Original 77.9 kB
After minification 66.3 kB
After compression 12.2 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 11.6 kB, which is 15% 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 65.7 kB or 84% of the original size.

Image Optimization

-9%

Potential reduce by 60.9 kB

Original 685.8 kB
After minification 624.9 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. WJRR images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 91.4 kB

Original 264.6 kB
After minification 264.5 kB
After compression 173.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 91.4 kB or 35% of the original size.

CSS Optimization

-31%

Potential reduce by 18.7 kB

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

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

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

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

High

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

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Requests the notification permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

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 Wjrr.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 Wjrr.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

wjrr.org

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

Report Summary

Performance

Accessibility

Best Practices

SEO

WJRR: High Impact Factor Journal| Research Paper Publication|Best International peer reviewed online open access Journal

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

wjrr.org

wjrr.org

main.css

cbdb-search-form.css

right_left_menu.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

wjrr.org

wjrr.org

main.css

cbdb-search-form.css

right_left_menu.css

style2.css

socal.css

styles.css

jsDatePick_ltr.min.css

jsapi

bootstrap.css

jquery.min.js

bootstrap.min.js

js

fabric-icons.css

jquery-1.7.1.min.js

jquery.nivo.slider.js

twitter.js

custom.js

modernizr.custom.28468.js

jquery.cslider.js

jquery.social.media.tabs.1.7.js

tabs.js

jquery.validate.js

jquery.complexify.js

script.js

jsDatePick.min.1.3.js

firebase-app.js

firebase-messaging.js

firebase-analytics.js

loader.js

fonts.css

web-style.css

twitter.css

transitions.css

media.css

prettyPhoto.css

46crossref-logo-200.png

btn_paynowCC_LG.gif

header-bg.jpg

scrolltop.png

settings.png

logo20.png