Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

re18.org

RE'18 - Home - 26th IEEE International Requirements Engineering Conference 2018, Banff, Alberta, Canada

Page Load Speed

48.6 sec in total

First Response

275 ms

Resources Loaded

48 sec

Page Rendered

384 ms

re18.org screenshot

About Website

Welcome to re18.org homepage info - get ready to check RE 18 best content right away, or after learning these important things about re18.org

http://re18.org/, 26th IEEE international, Requirements Engineering, Converence, August 20-24, Banff, Alberta, Canada

Visit re18.org

Key Findings

We analyzed Re18.org page load time and found that the first response time was 275 ms and then it took 48.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

re18.org performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.105

88/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

re18.org

275 ms

2477 ms

wombat.js

266 ms

AIT_Analytics.js

437 ms

disclaim-element.js

484 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Re18.org, 94% (99 requests) were made to Wayback.archive-it.org and 5% (5 requests) were made to Partner.archive-it.org. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Wayback.archive-it.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 643.4 kB (11%)

Content Size

5.7 MB

After Optimization

5.0 MB

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

HTML Optimization

-81%

Potential reduce by 53.1 kB

  • Original 65.4 kB
  • After minification 55.0 kB
  • After compression 12.3 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 16% 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 53.1 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 59.7 kB

  • Original 4.9 MB
  • After minification 4.9 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. RE 18 images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 264.1 kB

  • Original 360.5 kB
  • After minification 324.6 kB
  • After compression 96.4 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 264.1 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 266.5 kB

  • Original 313.3 kB
  • After minification 274.7 kB
  • After compression 46.8 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. Re18.org needs all CSS files to be minified and compressed as it can save up to 266.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (36%)

Requests Now

80

After Optimization

51

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

Accessibility Review

re18.org accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

re18.org SEO score

85

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

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

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

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