Tools & Wizards About Us

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

iiass.com

IIASS - Innovative Issues and Approaches in Social Sciences

Page Load Speed

2.5 sec in total

First Response

517 ms

Resources Loaded

1.8 sec

Page Rendered

223 ms

About Website

Click here to check amazing IIASS content. Otherwise, check out these important facts you probably never knew about iiass.com

IIASS is exclusively electronic peer reviewed journal that is published three times a year (initially in January, May and September)

Visit iiass.com

Key Findings

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

iiass.com performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

iiass.com

517 ms

newsletter.css

299 ms

mootools.js

296 ms

caption.js

201 ms

mod_image_slider.css

296 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 99% of them (73 requests) were addressed to the original Iiass.com, 1% (1 request) were made to Translate.google.com. The less responsive or slowest element that took the longest time to load (664 ms) belongs to the original domain Iiass.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.6 kB (13%)

Content Size

342.9 kB

After Optimization

298.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iiass.com main page is 342.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 256.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 41.4 kB

  • Original 51.5 kB
  • After minification 50.2 kB
  • After compression 10.1 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 41.4 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 202 B

  • Original 256.4 kB
  • After minification 256.2 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. IIASS images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 1.6 kB

  • Original 28.0 kB
  • After minification 28.0 kB
  • After compression 26.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-21%

Potential reduce by 1.5 kB

  • Original 7.0 kB
  • After minification 6.9 kB
  • After compression 5.5 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. Iiass.com needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (75%)

Requests Now

73

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

iiass.com accessibility score

87

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

Best Practices

iiass.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

iiass.com SEO score

69

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

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

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