Tools & Wizards About Us
imaginecup.am screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

imaginecup.am

Imagine Cup - Student Developer Tools, Resources and Experiences | Imagine Cup

Page Load Speed

3.2 sec in total

First Response

271 ms

Resources Loaded

2.7 sec

Page Rendered

221 ms

imaginecup.am screenshot

About Website

Click here to check amazing Imagine Cup content. Otherwise, check out these important facts you probably never knew about imaginecup.am

Bring your ideas to life. Find out how student developers can join Microsoft Imagine Cup, and elevate their skills with developer tools and resources.

Visit imaginecup.am

Key Findings

We analyzed Imaginecup.am page load time and found that the first response time was 271 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

imaginecup.am performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value2,330 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

imaginecup.am

271 ms

www.imaginecup.com

225 ms

www.imaginecup.com

1143 ms

css

150 ms

css

289 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Imaginecup.am, 52% (33 requests) were made to Imaginecup.com and 17% (11 requests) were made to Iccms.blob.core.windows.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Imaginecup.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.2 kB (64%)

Content Size

263.6 kB

After Optimization

94.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Imaginecup.am main page is 263.6 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. 40% of websites need less resources to load. Javascripts take 193.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.9 kB

  • Original 43.8 kB
  • After minification 37.6 kB
  • After compression 7.9 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 6.2 kB, which is 14% 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 35.9 kB or 82% of the original size.

Image Optimization

-36%

Potential reduce by 9.4 kB

  • Original 26.3 kB
  • After minification 16.8 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, Imagine Cup needs image optimization as it can save up to 9.4 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 123.9 kB

  • Original 193.5 kB
  • After minification 189.7 kB
  • After compression 69.6 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 123.9 kB or 64% 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 Imagine Cup. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

imaginecup.am

imaginecup.am

271 ms

www.imaginecup.com

www.imaginecup.com

225 ms

www.imaginecup.com

www.imaginecup.com

1143 ms

css

css

150 ms

css

css

289 ms

modernizr

modernizr

297 ms

jquery

jquery

434 ms

jqueryui

jqueryui

577 ms

Overrides

Overrides

293 ms

ICWebMain.js

ICWebMain.js

315 ms

Bootstrap.js

Bootstrap.js

40 ms

microsoftLogoForHeader.png

microsoftLogoForHeader.png

196 ms

MS_ICUP_logo_wht_no_star.png

MS_ICUP_logo_wht_no_star.png

81 ms

online_finals_hero-17e55c02f417.jpg

online_finals_hero-17e55c02f417.jpg

233 ms

comp_earth_sq-5b1b83b03387.jpg

comp_earth_sq-5b1b83b03387.jpg

148 ms

WIN13-SQ-2ce11754c019.png

WIN13-SQ-2ce11754c019.png

165 ms

IC-Competition-button-527f907734ec.jpg

IC-Competition-button-527f907734ec.jpg

147 ms

win10_imagine_ad-078feac6676f.png

win10_imagine_ad-078feac6676f.png

479 ms

Satya_sq-70d0002190c1.jpg

Satya_sq-70d0002190c1.jpg

149 ms

2016-HC3-SQ-a06757a7943d.jpg

2016-HC3-SQ-a06757a7943d.jpg

160 ms

2016-bi-plan-SQ-fbbdd690cd38.png

2016-bi-plan-SQ-fbbdd690cd38.png

165 ms

PROG-2-SQ-fcc58d1fa82a.jpg

PROG-2-SQ-fcc58d1fa82a.jpg

205 ms

PROG-1-SQ-a9ec745d56b2.jpg

PROG-1-SQ-a9ec745d56b2.jpg

172 ms

BID-sq-9de94a93bb52.png

BID-sq-9de94a93bb52.png

186 ms

search-button-blue.png

search-button-blue.png

72 ms

btn-FaceBook.png

btn-FaceBook.png

95 ms

btn-Twitter.png

btn-Twitter.png

73 ms

btn-LinkedIn.png

btn-LinkedIn.png

96 ms

L1FeatureRepeating.jpg

L1FeatureRepeating.jpg

73 ms

buttonHomeCommentsRest.png

buttonHomeCommentsRest.png

154 ms

windows_symbol_clr_52x52.png

windows_symbol_clr_52x52.png

145 ms

office_symbol_clr_52x52.png

office_symbol_clr_52x52.png

147 ms

fallpromo_bug_black.png

fallpromo_bug_black.png

147 ms

xbox_symbol_clr_52x52.png

xbox_symbol_clr_52x52.png

171 ms

skype_symbol_clr_52x52.png

skype_symbol_clr_52x52.png

170 ms

bing_symbol_clr_52x52.png

bing_symbol_clr_52x52.png

225 ms

store_symbol_clr_52x52.png

store_symbol_clr_52x52.png

225 ms

logo-type-1x.png

logo-type-1x.png

223 ms

serverComponent.php

serverComponent.php

48 ms

latest.woff

latest.woff

50 ms

latest.woff

latest.woff

66 ms

btn-facebook-hover.png

btn-facebook-hover.png

175 ms

btn-linkedin-hover.png

btn-linkedin-hover.png

199 ms

btn-twitter-hover.png

btn-twitter-hover.png

201 ms

btn-weibo-hover.png

btn-weibo-hover.png

245 ms

ajax-loader.gif

ajax-loader.gif

255 ms

ajax-loader-h.gif

ajax-loader-h.gif

244 ms

XP-Success.gif

XP-Success.gif

264 ms

XP-Warning.gif

XP-Warning.gif

293 ms

XP-Error.gif

XP-Error.gif

272 ms

17fa4fe0cacc0d421e21fd96829f73d3.js

17fa4fe0cacc0d421e21fd96829f73d3.js

10 ms

e2912c36d1ef85160f6bbc2ed36a282e.js

e2912c36d1ef85160f6bbc2ed36a282e.js

12 ms

9f043858df393e9d3af48654fc218f80.js

9f043858df393e9d3af48654fc218f80.js

32 ms

insight.min.js

insight.min.js

60 ms

bk-coretag.js

bk-coretag.js

47 ms

ms.js

ms.js

347 ms

c2076-pixel.js

c2076-pixel.js

47 ms

wtid.js

wtid.js

136 ms

favicon.ico

favicon.ico

47 ms

20206

20206

62 ms

general.js

general.js

12 ms

16365

16365

20 ms

dcs.gif

dcs.gif

74 ms

4499

4499

60 ms

Accessibility Review

imaginecup.am accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

imaginecup.am best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

imaginecup.am SEO score

76

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

High

robots.txt is not valid

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 Imaginecup.am 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 Imaginecup.am 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

imaginecup.am

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