1.7 sec in total
207 ms
1.4 sec
131 ms
Visit my.ohio.edu now to see the best up-to-date My OHIO content for United States and also check out these interesting facts you probably never knew about my.ohio.edu
My OHIO Portal at OHIO University based on uPortal
Visit my.ohio.eduWe analyzed My.ohio.edu page load time and found that the first response time was 207 ms and then it took 1.5 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.
my.ohio.edu performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value11.5 s
0/100
25%
Value8.7 s
16/100
10%
Value190 ms
91/100
30%
Value0.002
100/100
15%
Value11.6 s
18/100
10%
207 ms
68 ms
80 ms
113 ms
90 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 74% of them (62 requests) were addressed to the original My.ohio.edu, 25% (21 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (354 ms) belongs to the original domain My.ohio.edu.
Page size can be reduced by 1.4 MB (75%)
1.8 MB
465.9 kB
In fact, the total size of My.ohio.edu main page is 1.8 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. 65% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 44.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 44.9 kB or 78% of the original size.
Potential reduce by 6.6 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, My OHIO needs image optimization as it can save up to 6.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.0 MB
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 1.0 MB or 75% of the original size.
Potential reduce by 308.8 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. My.ohio.edu needs all CSS files to be minified and compressed as it can save up to 308.8 kB or 84% of the original size.
Number of requests can be reduced by 75 (91%)
82
7
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My OHIO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
render.uP
207 ms
css
68 ms
normalize-2.1.2.min.css
80 ms
font-awesome.min.css
113 ms
bootstrap-accessibility.min.css
90 ms
jquery-ui-1.10.3-smoothness.min.css
95 ms
modernizr-2.6.2.min.js
103 ms
jquery-1.10.2.min.js
87 ms
jquery-migrate-1.2.1.min.js
96 ms
jquery-ui-1.10.3.min.js
153 ms
bootstrap.min.js
180 ms
bootstrap-accessibility.min.js
150 ms
fluid-custom.min.js
201 ms
underscore-1.5.2.min.js
150 ms
backbone-1.1.0.min.js
188 ms
jquery.noty.packaged.min.js
189 ms
jquery.dataTables.min.js
193 ms
bootstrap-rating-input.min.js
189 ms
dataTables.bootstrap.js
189 ms
ColumnFilterWidgets.js
190 ms
resolve-conflicts.min.js
190 ms
up-util.js
191 ms
up-portlet-registry.js
190 ms
up-entity-registry.js
190 ms
up-portlet-browser.js
190 ms
up-layout-draggable-manager.js
190 ms
up-layout-gallery.js
190 ms
up-fragment-permissions-manager.js
333 ms
up-subscription-browser.js
332 ms
up-layout-selector.js
332 ms
up-skin-selector.js
349 ms
up-tab-manager.js
351 ms
up-layout-persistence.js
352 ms
up-url-provider.js
351 ms
up-layout-preferences.js
352 ms
up-autocomplete.js
353 ms
up-showHideToggle.js
354 ms
myOHIO.css
328 ms
tip.css
298 ms
bootstrap.min.css
290 ms
font-awesome.css
289 ms
announcements.css
281 ms
fineuploader-3.3.0.css
280 ms
attachments.css
276 ms
entity-selector.js
227 ms
up-parameter-editor.js
226 ms
flyout-nav.js
200 ms
up-translator.js
190 ms
up-sidebar-improved.js
190 ms
up-print-plugin.js
190 ms
up-ga.js
190 ms
up-rating-option.js
190 ms
up-favorite.js
190 ms
up-config-lightbox.js
189 ms
jquery.notice.min.js
188 ms
fineuploader-3.3.0.js
201 ms
furley_bg.png
32 ms
portal_logo.png
31 ms
icon-tip.png
23 ms
ui-icons_222222_256x240.png
24 ms
bullet_feed.png
123 ms
fontawesome-webfont.woff
122 ms
analytics.js
273 ms
GET-NOTIFICATIONS-UNCATEGORIZED.resource.uP
64 ms
collect
26 ms
collect
11 ms
collect
24 ms
collect
31 ms
collect
33 ms
collect
35 ms
collect
39 ms
collect
38 ms
collect
38 ms
collect
39 ms
collect
41 ms
collect
42 ms
collect
45 ms
collect
43 ms
collect
44 ms
collect
45 ms
collect
49 ms
collect
50 ms
collect
50 ms
collect
51 ms
my.ohio.edu 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
my.ohio.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
my.ohio.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 My.ohio.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 My.ohio.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.
my.ohio.edu
Open Graph description is not detected on the main page of My OHIO. 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: