Tools & Wizards About Us
eventedge.co screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

eventedge.co

Mobile Apps for Events, Conferences, and Corporate Meetings Made Simple | EventEdge

Page Load Speed

1.9 sec in total

First Response

126 ms

Resources Loaded

1.5 sec

Page Rendered

293 ms

eventedge.co screenshot

About Website

Click here to check amazing Event Edge content. Otherwise, check out these important facts you probably never knew about eventedge.co

Our customized, world class event apps are perfect for meetings and conferences big and small. Revolutionize your attendees experience by getting started today.

Visit eventedge.co

Key Findings

We analyzed Eventedge.co page load time and found that the first response time was 126 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

eventedge.co performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value2,970 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.324

35/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

eventedge.co

126 ms

www.eventedge.co

114 ms

www.eventedge.co

247 ms

main.css

58 ms

style.css

115 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 55% of them (60 requests) were addressed to the original Eventedge.co, 17% (18 requests) were made to Platform.twitter.com and 9% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (471 ms) belongs to the original domain Eventedge.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (63%)

Content Size

1.7 MB

After Optimization

613.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eventedge.co main page is 1.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 37.4 kB

  • Original 46.2 kB
  • After minification 34.5 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. This page needs HTML code to be minified as it can gain 11.8 kB, which is 25% 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 37.4 kB or 81% of the original size.

Image Optimization

-78%

Potential reduce by 815.0 kB

  • Original 1.0 MB
  • After minification 224.1 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. Obviously, Event Edge needs image optimization as it can save up to 815.0 kB or 78% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-35%

Potential reduce by 195.1 kB

  • Original 560.6 kB
  • After minification 527.5 kB
  • After compression 365.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 195.1 kB or 35% of the original size.

CSS Optimization

-34%

Potential reduce by 7.5 kB

  • Original 22.1 kB
  • After minification 22.1 kB
  • After compression 14.6 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. Eventedge.co needs all CSS files to be minified and compressed as it can save up to 7.5 kB or 34% of the original size.

Requests Breakdown

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

Requests Now

93

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eventedge.co

eventedge.co

126 ms

www.eventedge.co

www.eventedge.co

114 ms

www.eventedge.co

www.eventedge.co

247 ms

main.css

main.css

58 ms

style.css

style.css

115 ms

css

css

32 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

271 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

167 ms

custom.min.js

custom.min.js

269 ms

jquery.htm

jquery.htm

165 ms

cufon-yui.js

cufon-yui.js

174 ms

Calibri_700.font.js

Calibri_700.font.js

234 ms

PragmaticaCTT_400.font.js

PragmaticaCTT_400.font.js

285 ms

PragmaticaLightC_200.font.js

PragmaticaLightC_200.font.js

222 ms

cufon-replace.js

cufon-replace.js

231 ms

twitter.js

twitter.js

285 ms

testimonial.css

testimonial.css

288 ms

modernizr.js

modernizr.js

304 ms

testimonial.js

testimonial.js

326 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

325 ms

jquery.fancybox.css

jquery.fancybox.css

326 ms

video.js

video.js

335 ms

flexslider-min.js

flexslider-min.js

344 ms

custom.js

custom.js

358 ms

common.css

common.css

380 ms

style5.css

style5.css

381 ms

api.js

api.js

38 ms

noform.js

noform.js

118 ms

css

css

19 ms

jsapi

jsapi

6 ms

bg.gif

bg.gif

98 ms

loader.js

loader.js

26 ms

ss.js

ss.js

20 ms

logo.jpg

logo.jpg

67 ms

s-icon.png

s-icon.png

66 ms

loading.gif

loading.gif

66 ms

1395367543-waitingfor2.png

1395367543-waitingfor2.png

374 ms

1395367260-musthave.png

1395367260-musthave.png

382 ms

1490732553-instant.jpg

1490732553-instant.jpg

127 ms

aep-img.png

aep-img.png

127 ms

video-eventedge.jpg

video-eventedge.jpg

127 ms

video-caption-bg.png

video-caption-bg.png

126 ms

internet-connection-icon.png

internet-connection-icon.png

216 ms

backend-system-icon.png

backend-system-icon.png

216 ms

head-phone-icon.png

head-phone-icon.png

217 ms

easy-to-get-started-img.png

easy-to-get-started-img.png

217 ms

simple-management.png

simple-management.png

276 ms

instant-feedback-img.png

instant-feedback-img.png

276 ms

save-time-money.png

save-time-money.png

276 ms

f-1.png

f-1.png

275 ms

bg.jpg

bg.jpg

337 ms

f-2.png

f-2.png

338 ms

f-3.png

f-3.png

341 ms

f-4.png

f-4.png

340 ms

f-5.png

f-5.png

390 ms

yahoo-logo.png

yahoo-logo.png

391 ms

wbcsd-logo.png

wbcsd-logo.png

390 ms

radio-shack-logo.png

radio-shack-logo.png

393 ms

tjf-logo.png

tjf-logo.png

469 ms

mc-logo.png

mc-logo.png

469 ms

fore-see-logo.png

fore-see-logo.png

470 ms

mi-logo.png

mi-logo.png

471 ms

follow-us-on-twitter.jpg

follow-us-on-twitter.jpg

471 ms

koi

koi

151 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

42 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

43 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

62 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

102 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

81 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

101 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

101 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

91 ms

arrow-down.gif

arrow-down.gif

402 ms

widgets.js

widgets.js

46 ms

ga.js

ga.js

81 ms

dc.js

dc.js

111 ms

user_timeline.json

user_timeline.json

213 ms

scroll-to-top.png

scroll-to-top.png

397 ms

recaptcha__en.js

recaptcha__en.js

105 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

67 ms

__utm.gif

__utm.gif

80 ms

__utm.gif

__utm.gif

78 ms

settings

settings

133 ms

fallback

fallback

30 ms

fallback

fallback

66 ms

fallback__ltr.css

fallback__ltr.css

4 ms

css

css

17 ms

logo_48.png

logo_48.png

4 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

5 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

5 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

4 ms

eventmobile

eventmobile

37 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

4 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

18 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

24 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

21 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

23 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

48 ms

_buildManifest.js

_buildManifest.js

22 ms

_ssgManifest.js

_ssgManifest.js

23 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

13 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

12 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

11 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

10 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

5 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

22 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

9 ms

bullets.png

bullets.png

59 ms

next_prev.png

next_prev.png

58 ms

Accessibility Review

eventedge.co accessibility score

61

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

eventedge.co best practices score

67

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

Browser errors were logged to the console

SEO Factors

eventedge.co SEO score

75

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

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eventedge.co can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eventedge.co 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

eventedge.co

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