2.3 sec in total
63 ms
2 sec
182 ms
Welcome to oberlinproject.org homepage info - get ready to check Oberlin Project best content right away, or after learning these important things about oberlinproject.org
The Oberlin Project's aim is to revitalize the local economy, eliminate carbon emissions, restore local agriculture, food supply and forestry, and create a new, sustainable base for economic and commu...
Visit oberlinproject.orgWe analyzed Oberlinproject.org page load time and found that the first response time was 63 ms and then it took 2.2 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.
oberlinproject.org performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value7.2 s
5/100
25%
Value5.7 s
51/100
10%
Value160 ms
94/100
30%
Value0.173
69/100
15%
Value9.3 s
32/100
10%
63 ms
154 ms
127 ms
146 ms
141 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 73% of them (87 requests) were addressed to the original Oberlinproject.org, 10% (12 requests) were made to Static.xx.fbcdn.net and 3% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (752 ms) belongs to the original domain Oberlinproject.org.
Page size can be reduced by 56.9 kB (4%)
1.6 MB
1.5 MB
In fact, the total size of Oberlinproject.org main page is 1.6 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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 41.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 41.7 kB or 76% of the original size.
Potential reduce by 9.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. Oberlin Project images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 3.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. Oberlinproject.org has all CSS files already compressed.
Number of requests can be reduced by 74 (66%)
112
38
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oberlin Project. 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 34 to 1 for CSS and as a result speed up the page load time.
oberlinproject.org
63 ms
oberlinproject.org
154 ms
modal.css
127 ms
template.css
146 ms
content_style.css
141 ms
style.css
138 ms
typo.css
128 ms
jcemediabox.css
139 ms
style.css
238 ms
widgetkit-b36d382d.css
242 ms
base.css
253 ms
grid.css
273 ms
type.css
265 ms
forms.css
287 ms
superfish.css
361 ms
fonts.css
371 ms
k2.css
368 ms
theme.css
394 ms
hilite-top.css
387 ms
mediaqueries.css
403 ms
css-c7c3796ae47eb65ea19b76161648d979.php
481 ms
custom.css
489 ms
style.css
508 ms
module.css
511 ms
fancybox.css
519 ms
style.css
595 ms
sky.css
598 ms
css
35 ms
css
50 ms
css
57 ms
css
55 ms
15120f5172043bfc29429097647a4480.css
604 ms
zentools.css
618 ms
mootools-core.js
632 ms
core.js
630 ms
mootools-more.js
716 ms
modal.js
713 ms
jquery-1.7.1.min.js
734 ms
k2.js
741 ms
jquery-1.7.0.min.js
687 ms
script.js
33 ms
widgets.js
20 ms
noconflict.js
752 ms
jquery.cookie.js
695 ms
superfish.js
701 ms
jquery.hoverIntent.minified.js
698 ms
slide.js
709 ms
template.js
712 ms
behaviour.js
740 ms
jwplayer.js
707 ms
silverlight.js
711 ms
wmvplayer.js
695 ms
AC_QuickTime.js
700 ms
script.js
698 ms
jcemediabox.js
715 ms
widgetkit-5c88cfcf.js
710 ms
296b9255855c2e34d5e307fbb2b75c55.js
707 ms
sh404sefsocial.js
704 ms
lightbox.js
133 ms
mediaelement-and-player.js
149 ms
spotlight.js
121 ms
logo.png
121 ms
bikes-slowtrain-1200px.jpg
120 ms
tappan-square-trees-1200px.jpg
121 ms
grasses-and-flowers-1200px.jpg
270 ms
Oberlin-tappan-memorial-1200px.jpg
269 ms
oberlin-downtown-1200px.jpg
299 ms
city-of-oberlin-logo.png
269 ms
oberlin-college-logo.png
270 ms
Climate_Positive_Participant-Logo.jpg
271 ms
twitter.png
361 ms
facebook.png
351 ms
youtube.png
363 ms
twitterStrip.png
361 ms
facebookStrip.png
393 ms
all.js
17 ms
greyOverlay.png
414 ms
topsl-bg.gif
455 ms
community-engagement-slide.jpg
471 ms
newoberlindash.jpg
466 ms
climate-positive-slide.jpg
467 ms
local-food-slide.jpg
515 ms
transportation-slide.jpg
520 ms
local-land-slide.jpg
614 ms
economic-development-slide.jpg
574 ms
education-slide.jpg
587 ms
arrowleft.png
586 ms
dot.png
636 ms
arrowright.png
638 ms
15120f5172043bfc29429097647a4480.css
586 ms
51937704
300 ms
allvideos_v4_bg_1000x550.jpg
700 ms
BngSUXNadjH0qYEzV7ab-oWlsbg95AiFW_jCRs-2.ttf
47 ms
all.js
34 ms
connect.php
103 ms
topsl1-bg.png
671 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
33 ms
13d4b03af751995b7b81994b08079326.png
648 ms
toTop.png
682 ms
46 ms
settings
76 ms
e_HgBmX_maw.css
15 ms
pG38x2t_cJf.css
79 ms
iCuydckKNSp.css
22 ms
Zi20d5DVxmM.js
28 ms
button.856debeac157d9669cf51e73a08fbc93.js
6 ms
embeds
81 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.en-gb.html
12 ms
Mw5y7Z3v-mj.js
30 ms
css;base64,
5 ms
css;%20charset=utf-8;base64,I2Jvb3Rsb2FkZXJfUF9tcjVWRXtoZWlnaHQ6NDJweDt9LmJvb3Rsb2FkZXJfUF9tcjVWRXtkaXNwbGF5OmJsb2NrIWltcG9ydGFudDt9
5 ms
p1JdCuHb-VX.gif
29 ms
_66GK_srv0g.png
33 ms
o1ndYS2og_B.js
2 ms
pLoSlJD7y1F.js
4 ms
8IAOdJiZGNE.js
9 ms
X7GNFODmu6E.js
10 ms
qvzskUrYlYC.js
10 ms
api.js
16 ms
hsts-pixel.gif
4 ms
oberlinproject.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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
oberlinproject.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
oberlinproject.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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 Oberlinproject.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 Oberlinproject.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.
oberlinproject.org
Open Graph description is not detected on the main page of Oberlin Project. 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: