Tools & Wizards About Us
awe2017.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

awe2017.com

AWE USA 2017 - the world's largest AR & VR event

Page Load Speed

2.1 sec in total

First Response

124 ms

Resources Loaded

1.2 sec

Page Rendered

768 ms

awe2017.com screenshot

About Website

Click here to check amazing AWE 2017 content. Otherwise, check out these important facts you probably never knew about awe2017.com

Join over 5,000 AR & VR professionals at the 8th annual AWE in Santa Clara, California on May 31 - June 2, 2017.

Visit awe2017.com

Key Findings

We analyzed Awe2017.com page load time and found that the first response time was 124 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

awe2017.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

3/100

10%

LCP (Largest Contentful Paint)

Value42.9 s

0/100

25%

SI (Speed Index)

Value28.8 s

0/100

10%

TBT (Total Blocking Time)

Value2,260 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value40.6 s

0/100

10%

Network Requests Diagram

awe2017.com

124 ms

css

27 ms

style-f7b4398e348fd721fc8375943af55eae.css

519 ms

trade20e7.css

132 ms

css

38 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 58% of them (33 requests) were addressed to the original Awe2017.com, 11% (6 requests) were made to Youtube.com and 11% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (630 ms) belongs to the original domain Awe2017.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.2 MB (41%)

Content Size

10.3 MB

After Optimization

6.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Awe2017.com main page is 10.3 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. Only a small number of websites need less resources to load. Images take 9.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 48.9 kB

  • Original 56.3 kB
  • After minification 40.2 kB
  • After compression 7.4 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 16.2 kB, which is 29% 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 48.9 kB or 87% of the original size.

Image Optimization

-39%

Potential reduce by 3.6 MB

  • Original 9.4 MB
  • After minification 5.8 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. Obviously, AWE 2017 needs image optimization as it can save up to 3.6 MB or 39% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 2.5 kB

  • Original 159.2 kB
  • After minification 159.2 kB
  • After compression 156.7 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

-79%

Potential reduce by 494.0 kB

  • Original 628.8 kB
  • After minification 498.9 kB
  • After compression 134.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. Awe2017.com needs all CSS files to be minified and compressed as it can save up to 494.0 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (22%)

Requests Now

49

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

awe2017.com

awe2017.com

124 ms

css

css

27 ms

style-f7b4398e348fd721fc8375943af55eae.css

style-f7b4398e348fd721fc8375943af55eae.css

519 ms

trade20e7.css

trade20e7.css

132 ms

css

css

38 ms

custom.css

custom.css

108 ms

jar7y2fv2amexqutq1w1.png

jar7y2fv2amexqutq1w1.png

66 ms

jar7y2fv2amexqutq1w1.png

jar7y2fv2amexqutq1w1.png

63 ms

bizzabo-loader.gif

bizzabo-loader.gif

72 ms

vg2bshd5iu5fgfw7qhk6.png

vg2bshd5iu5fgfw7qhk6.png

526 ms

i02jk51ybdgcfterptqu.png

i02jk51ybdgcfterptqu.png

77 ms

bral34qhmg9itcrrdgxr.png

bral34qhmg9itcrrdgxr.png

229 ms

reonjbmznh20m6xtstrg.jpg

reonjbmznh20m6xtstrg.jpg

495 ms

ywpnkijaonxwmkc3iry7.jpg

ywpnkijaonxwmkc3iry7.jpg

382 ms

zrndafoig5kddp5ws4nc.jpg

zrndafoig5kddp5ws4nc.jpg

381 ms

p0cCSr6SjSj2QFqLLuQT_Inspire-TEE.png

p0cCSr6SjSj2QFqLLuQT_Inspire-TEE.png

527 ms

MoQbFT0QfmFe8UeT3p1R_Design-TEE2.png

MoQbFT0QfmFe8UeT3p1R_Design-TEE2.png

527 ms

QXR1CoTaR5aQRNwcsuAW_Develop-TEE.png

QXR1CoTaR5aQRNwcsuAW_Develop-TEE.png

526 ms

4OPxgZXwSfe68fp2pEFU_Work-TEE-2.png

4OPxgZXwSfe68fp2pEFU_Work-TEE-2.png

587 ms

2qQSSNIVSHe27SAwVEgt_Life-TEE.png

2qQSSNIVSHe27SAwVEgt_Life-TEE.png

589 ms

oZif7uoCSamSnyiAdNK7_Startup-TEE.png

oZif7uoCSamSnyiAdNK7_Startup-TEE.png

587 ms

awe2017.com

awe2017.com

587 ms

AVR0WmWRSyKerIIqEYil_5Grid-TEE.png

AVR0WmWRSyKerIIqEYil_5Grid-TEE.png

591 ms

rbf0nonmqjcitsbo6y4u.png

rbf0nonmqjcitsbo6y4u.png

589 ms

lbdjfklswilt03q6lllj.jpg

lbdjfklswilt03q6lllj.jpg

592 ms

rl6q53yibimbnhr3uqjc.jpg

rl6q53yibimbnhr3uqjc.jpg

590 ms

fmuc73qi04lahx7acdeq.jpg

fmuc73qi04lahx7acdeq.jpg

592 ms

586544-a901bc83a8b6cf1b44e046d7b7fea7cd.html

586544-a901bc83a8b6cf1b44e046d7b7fea7cd.html

80 ms

bqq7vlyrz6bkry5ihto1.png

bqq7vlyrz6bkry5ihto1.png

574 ms

kknxbxvtd0xytddvsjxh.jpg

kknxbxvtd0xytddvsjxh.jpg

572 ms

myvg8saj9rsaorjjom9u.jpg

myvg8saj9rsaorjjom9u.jpg

574 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

19 ms

bootstrap.min.js

bootstrap.min.js

30 ms

c1hfol5xreivub0xqh94.jpg

c1hfol5xreivub0xqh94.jpg

572 ms

dwhwc44s84o3887qfeos.jpg

dwhwc44s84o3887qfeos.jpg

630 ms

dzcrxkxkxu7in00cdbwx.jpg

dzcrxkxkxu7in00cdbwx.jpg

629 ms

o1mbeh7gi84fkg052hix.jpg

o1mbeh7gi84fkg052hix.jpg

629 ms

lb523watfvrjxacykjax.jpg

lb523watfvrjxacykjax.jpg

629 ms

DamMMCI25Ws

DamMMCI25Ws

127 ms

videoseries

videoseries

483 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

25 ms

base.js

base.js

50 ms

ad_status.js

ad_status.js

338 ms

QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js

QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js

337 ms

embed.js

embed.js

233 ms

id

id

62 ms

SPaD-ZQso7hhwM-LbdblRqaALiVxNcrDKAgLwj1ps2HF87LQBMTTDCiLeBD1LGQSkuvP4ZV_gXE=s68-c-k-c0x00ffffff-no-rj

SPaD-ZQso7hhwM-LbdblRqaALiVxNcrDKAgLwj1ps2HF87LQBMTTDCiLeBD1LGQSkuvP4ZV_gXE=s68-c-k-c0x00ffffff-no-rj

271 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

262 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

263 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

352 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

379 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

379 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

384 ms

bizzafont-3185a62de562f46ac19e4d753f76e121.woff

bizzafont-3185a62de562f46ac19e4d753f76e121.woff

356 ms

Create

Create

209 ms

Create

Create

357 ms

Accessibility Review

awe2017.com accessibility score

52

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.

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

Image elements do not have [alt] attributes

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

awe2017.com best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

awe2017.com SEO score

74

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Awe2017.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 Awe2017.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

awe2017.com

Open Graph data is detected on the main page of AWE 2017. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: