Tools & Wizards About Us
sura.org screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

sura.org

SURA (Southeastern Universities Research Association)

Page Load Speed

2.4 sec in total

First Response

145 ms

Resources Loaded

1.6 sec

Page Rendered

638 ms

sura.org screenshot

About Website

Click here to check amazing SURA content for United States. Otherwise, check out these important facts you probably never knew about sura.org

SURA enables the advancement of Big Science, large scale leading-edge research, and industry innovations.

Visit sura.org

Key Findings

We analyzed Sura.org page load time and found that the first response time was 145 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

sura.org performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value18.3 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.594

11/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

sura.org

145 ms

sura.org

348 ms

formidableforms.css

125 ms

mediaelementplayer-legacy.min.css

179 ms

wp-mediaelement.min.css

180 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 77% of them (65 requests) were addressed to the original Sura.org, 17% (14 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (663 ms) belongs to the original domain Sura.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 430.9 kB (33%)

Content Size

1.3 MB

After Optimization

862.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sura.org main page is 1.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. 60% of websites need less resources to load. Javascripts take 458.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 227.4 kB

  • Original 268.3 kB
  • After minification 264.5 kB
  • After compression 40.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. 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 227.4 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 100 B

  • Original 426.0 kB
  • After minification 425.9 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. SURA images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 155.6 kB

  • Original 458.5 kB
  • After minification 458.5 kB
  • After compression 302.9 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 155.6 kB or 34% of the original size.

CSS Optimization

-34%

Potential reduce by 47.8 kB

  • Original 140.7 kB
  • After minification 138.5 kB
  • After compression 92.9 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. Sura.org needs all CSS files to be minified and compressed as it can save up to 47.8 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (91%)

Requests Now

66

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sura.org

sura.org

145 ms

sura.org

sura.org

348 ms

formidableforms.css

formidableforms.css

125 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

179 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

180 ms

general.min.css

general.min.css

183 ms

style.min.css

style.min.css

181 ms

multiple-select.min.css

multiple-select.min.css

180 ms

style.min.css

style.min.css

185 ms

styles.css

styles.css

418 ms

style.css

style.css

302 ms

style.css

style.css

312 ms

css

css

37 ms

dynamic-mobmenu.css

dynamic-mobmenu.css

179 ms

css

css

25 ms

css

css

35 ms

default.css

default.css

180 ms

intlTelInput.min.css

intlTelInput.min.css

185 ms

style.min.css

style.min.css

258 ms

mobmenu-icons.css

mobmenu-icons.css

250 ms

mobmenu.css

mobmenu.css

259 ms

style.css

style.css

300 ms

jquery.min.js

jquery.min.js

369 ms

jquery-migrate.min.js

jquery-migrate.min.js

314 ms

mobmenu.js

mobmenu.js

304 ms

et-core-unified-18941.min.css

et-core-unified-18941.min.css

308 ms

owl.carousel.css

owl.carousel.css

358 ms

sa-owl-theme.css

sa-owl-theme.css

364 ms

animate.min.css

animate.min.css

425 ms

lightgallery.css

lightgallery.css

426 ms

lightgallery-bundle.min.css

lightgallery-bundle.min.css

427 ms

script.min.js

script.min.js

427 ms

multiple-select.min.js

multiple-select.min.js

484 ms

script.min.js

script.min.js

433 ms

index.js

index.js

441 ms

index.js

index.js

442 ms

scripts.js

scripts.js

481 ms

element.js

element.js

49 ms

dlm-xhr.min.js

dlm-xhr.min.js

487 ms

idle-timer.min.js

idle-timer.min.js

489 ms

custom.js

custom.js

500 ms

e-202424.js

e-202424.js

16 ms

scripts.min.js

scripts.min.js

610 ms

jquery.fitvids.js

jquery.fitvids.js

481 ms

jquery.mobile.js

jquery.mobile.js

445 ms

easypiechart.js

easypiechart.js

454 ms

salvattore.js

salvattore.js

444 ms

new-tab.js

new-tab.js

455 ms

common.js

common.js

496 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

501 ms

intlTelInput.min.js

intlTelInput.min.js

450 ms

script.min.js

script.min.js

455 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

511 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

429 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

432 ms

owl.carousel.min.js

owl.carousel.min.js

431 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

432 ms

owl.carousel2.thumbs.min.js

owl.carousel2.thumbs.min.js

440 ms

lightgallery.min.js

lightgallery.min.js

454 ms

lg-video.min.js

lg-video.min.js

450 ms

lg-zoom.min.js

lg-zoom.min.js

444 ms

lg-autoplay.min.js

lg-autoplay.min.js

439 ms

player.min.js

player.min.js

404 ms

SURA-HOMEPAGE-WHY_TIER1.jpg

SURA-HOMEPAGE-WHY_TIER1.jpg

663 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff

22 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

27 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

42 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

46 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

49 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

48 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

47 ms

modules.woff

modules.woff

510 ms

et-divi-dynamic-tb-14554-tb-14636-18941-late.css

et-divi-dynamic-tb-14554-tb-14636-18941-late.css

370 ms

sura-logo.png

sura-logo.png

85 ms

icon_prev.png

icon_prev.png

63 ms

icon_next.png

icon_next.png

62 ms

modules.woff

modules.woff

68 ms

Accessibility Review

sura.org accessibility score

73

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Heading elements are not in a sequentially-descending order

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

sura.org 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

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

sura.org SEO score

74

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

Page is blocked from indexing

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 Sura.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 Sura.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

sura.org

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