Tools & Wizards About Us
embark.unc.edu screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    44% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

embark.unc.edu

Embark Carolina | Find Funding & Global Opportunities

Page Load Speed

2.8 sec in total

First Response

410 ms

Resources Loaded

1.7 sec

Page Rendered

731 ms

embark.unc.edu screenshot

About Website

Visit embark.unc.edu now to see the best up-to-date Embark Unc content for United States and also check out these interesting facts you probably never knew about embark.unc.edu

Search awards, scholarships and fellowships in our interactive Funding Finder. Explore and navigate global opportunities in the Global Guide.

Visit embark.unc.edu

Key Findings

We analyzed Embark.unc.edu page load time and found that the first response time was 410 ms and then it took 2.4 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

embark.unc.edu performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

embark.unc.edu

410 ms

wp-emoji-release.min.js

30 ms

toolset-common-es.css

53 ms

style.css

113 ms

bootstrap.min.css

236 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 79% of them (44 requests) were addressed to the original Embark.unc.edu, 7% (4 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (661 ms) belongs to the original domain Embark.unc.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 639.4 kB (22%)

Content Size

2.9 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Embark.unc.edu main page is 2.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. 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 21.5 kB

  • Original 29.1 kB
  • After minification 27.2 kB
  • After compression 7.7 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 21.5 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 86.6 kB

  • Original 2.1 MB
  • After minification 2.0 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. Embark Unc images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 146.3 kB

  • Original 256.4 kB
  • After minification 233.5 kB
  • After compression 110.1 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 146.3 kB or 57% of the original size.

CSS Optimization

-78%

Potential reduce by 385.1 kB

  • Original 490.5 kB
  • After minification 479.9 kB
  • After compression 105.5 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. Embark.unc.edu needs all CSS files to be minified and compressed as it can save up to 385.1 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (70%)

Requests Now

50

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

embark.unc.edu

embark.unc.edu

410 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

30 ms

toolset-common-es.css

toolset-common-es.css

53 ms

style.css

style.css

113 ms

bootstrap.min.css

bootstrap.min.css

236 ms

font-awesome.min.css

font-awesome.min.css

125 ms

common-skeleton.min.css

common-skeleton.min.css

115 ms

tooltip.min.css

tooltip.min.css

90 ms

style.min.css

style.min.css

111 ms

views-frontend.css

views-frontend.css

148 ms

dashicons.min.css

dashicons.min.css

160 ms

select2.css

select2.css

146 ms

toolset_maps_fixes.css

toolset_maps_fixes.css

148 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

143 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

169 ms

wpv-pagination.css

wpv-pagination.css

166 ms

ebs_dynamic_css.php

ebs_dynamic_css.php

166 ms

main.min.css

main.min.css

313 ms

jquery.min.js

jquery.min.js

58 ms

bootstrap.min.js

bootstrap.min.js

244 ms

modernizr-2.7.0.min.js

modernizr-2.7.0.min.js

245 ms

utility-bar.min.js

utility-bar.min.js

58 ms

core.min.js

core.min.js

243 ms

datepicker.min.js

datepicker.min.js

247 ms

underscore-before.js

underscore-before.js

241 ms

underscore.min.js

underscore.min.js

266 ms

underscore-after.js

underscore-after.js

239 ms

suggest.min.js

suggest.min.js

241 ms

main.js

main.js

275 ms

date.js

date.js

264 ms

js

js

127 ms

jquery.wpvmap.js

jquery.wpvmap.js

264 ms

jquery.fitvids.js

jquery.fitvids.js

263 ms

scripts.min.js

scripts.min.js

326 ms

wp-embed.min.js

wp-embed.min.js

285 ms

css

css

112 ms

css

css

27 ms

css

css

41 ms

search-icon.svg

search-icon.svg

271 ms

Embark-banner-pink-1-1.png

Embark-banner-pink-1-1.png

661 ms

Isogrid_2_final_v3.png

Isogrid_2_final_v3.png

304 ms

embark-logo.svg

embark-logo.svg

247 ms

horizontal-stripe@2x.png

horizontal-stripe@2x.png

269 ms

Keeshawn-IMG_3185-jpg.jpg

Keeshawn-IMG_3185-jpg.jpg

301 ms

footer-bg.png

footer-bg.png

285 ms

center-logo-vertical.svg

center-logo-vertical.svg

264 ms

twitter.svg

twitter.svg

257 ms

facebook.svg

facebook.svg

265 ms

instagram.svg

instagram.svg

266 ms

unc-global-white.svg

unc-global-white.svg

268 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

182 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo.woff

182 ms

NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzZQ.woff

NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzZQ.woff

285 ms

NaPecZTIAOhVxoMyOr9n_E7fdMPmCw.woff

NaPecZTIAOhVxoMyOr9n_E7fdMPmCw.woff

287 ms

gen_204

gen_204

170 ms

analytics.js

analytics.js

160 ms

Accessibility Review

embark.unc.edu accessibility score

78

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

embark.unc.edu 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

embark.unc.edu SEO score

93

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

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

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 Embark.unc.edu 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 Embark.unc.edu 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

embark.unc.edu

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