Tools & Wizards About Us

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

infocom2017.ieee-infocom.org

IEEE INFOCOM 2017 | 1-4 May 2017 // Atlanta, GA, USA

Page Load Speed

830 ms in total

First Response

29 ms

Resources Loaded

571 ms

Page Rendered

230 ms

About Website

Click here to check amazing INFOCOM 2017 IEEE content for United States. Otherwise, check out these important facts you probably never knew about infocom2017.ieee-infocom.org

IEEE INFOCOM is a top ranked conference on networking in the research community. It is a major conference venue for researchers to present and exchange significant and innovative contributions and ide...

Visit infocom2017.ieee-infocom.org

Key Findings

We analyzed Infocom2017.ieee-infocom.org page load time and found that the first response time was 29 ms and then it took 801 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

infocom2017.ieee-infocom.org performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

infocom2017.ieee-infocom.org

29 ms

fbds.js

27 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

7 ms

css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css

20 ms

css_qqb4MUh035zMlC_3pAP2q955ZaQy-AsrjtUu8nPluc0.css

20 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 83% of them (43 requests) were addressed to the original Infocom2017.ieee-infocom.org, 4% (2 requests) were made to Cdnjs.cloudflare.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (292 ms) relates to the external source S3-us-west-2.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 595.6 kB (31%)

Content Size

1.9 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Infocom2017.ieee-infocom.org main page is 1.9 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 30.3 kB

  • Original 39.0 kB
  • After minification 36.6 kB
  • After compression 8.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 30.3 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 41.9 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. INFOCOM 2017 IEEE images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 167.0 kB

  • Original 234.2 kB
  • After minification 202.8 kB
  • After compression 67.3 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 167.0 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 356.4 kB

  • Original 413.5 kB
  • After minification 403.6 kB
  • After compression 57.0 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. Infocom2017.ieee-infocom.org needs all CSS files to be minified and compressed as it can save up to 356.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (48%)

Requests Now

48

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

infocom2017.ieee-infocom.org accessibility score

72

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.

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 IDs are not unique

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

High

Links do not have a discernible name

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

infocom2017.ieee-infocom.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

infocom2017.ieee-infocom.org SEO score

77

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

Links are not crawlable

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 Infocom2017.ieee-infocom.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 Infocom2017.ieee-infocom.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 INFOCOM 2017 IEEE. 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: