1.7 sec in total
99 ms
1 sec
533 ms
Visit cur.org now to see the best up-to-date Cur content for United States and also check out these interesting facts you probably never knew about cur.org
Visit the Council on Undergraduate Research home page. View information about membership, publications, conferences, projects, governance, advocacy and more.
Visit cur.orgWe analyzed Cur.org page load time and found that the first response time was 99 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
cur.org performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value6.6 s
8/100
25%
Value6.4 s
41/100
10%
Value270 ms
82/100
30%
Value0.185
66/100
15%
Value14.0 s
10/100
10%
99 ms
392 ms
145 ms
193 ms
76 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 96% of them (55 requests) were addressed to the original Cur.org, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (392 ms) belongs to the original domain Cur.org.
Page size can be reduced by 578.6 kB (54%)
1.1 MB
484.0 kB
In fact, the total size of Cur.org main page is 1.1 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. 30% of websites need less resources to load. Javascripts take 500.6 kB which makes up the majority of the site volume.
Potential reduce by 90.1 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.1 kB, which is 15% 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 90.1 kB or 83% of the original size.
Potential reduce by 21.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. Cur images are well optimized though.
Potential reduce by 370.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 370.1 kB or 74% of the original size.
Potential reduce by 97.3 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. Cur.org needs all CSS files to be minified and compressed as it can save up to 97.3 kB or 86% of the original size.
Number of requests can be reduced by 32 (62%)
52
20
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cur. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
cur.org
99 ms
www.cur.org
392 ms
style.css
145 ms
jquery-core-plugins.js
193 ms
jquery-functions.js
76 ms
functionsC.js
116 ms
WebResource.axd
116 ms
events.js
106 ms
jquery.cycle.all.min.js
177 ms
swfobject.js
132 ms
ScriptResource.axd
155 ms
ScriptResource.axd
224 ms
ScriptResource.axd
144 ms
thickbox.css
100 ms
jquery-thickbox.js
172 ms
bg.gif
29 ms
ga.js
53 ms
spacer.gif
45 ms
tagline.gif
46 ms
URW-Swoosh.jpg
183 ms
HandsRaised-Swoosh.jpg
168 ms
BannerNOinfo(1).jpg
98 ms
Banner1.JPG
184 ms
World-Swoosh1.JPG
197 ms
rss.png
100 ms
fellows_photo.jpg
105 ms
fall-2014-v35.1CoverSm.jpg
165 ms
CUR.gif
164 ms
faceico.jpg
181 ms
ncurashe600.jpg
297 ms
headerback.png
187 ms
logo.gif
182 ms
search.png
169 ms
searchgo.png
171 ms
loginbox.jpg
187 ms
btnMed.gif
190 ms
mainNavBg.png
194 ms
navlcorner.png
225 ms
navrcorner.png
229 ms
subgreen.gif
210 ms
subblue.gif
214 ms
subyellow.gif
216 ms
suborange.gif
235 ms
subred.gif
236 ms
subpurple.gif
238 ms
subsky.gif
265 ms
subplum.gif
270 ms
__utm.gif
69 ms
pause.gif
223 ms
slideshowprev.gif
203 ms
slideshownext.gif
204 ms
topborder.gif
244 ms
eventdate3.gif
235 ms
go.jpg
234 ms
mainbottom.gif
252 ms
loadingAnimation.gif
206 ms
slidenav.gif
192 ms
cur.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
cur.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
cur.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cur.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 Cur.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.
cur.org
Open Graph description is not detected on the main page of Cur. 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: