2.2 sec in total
66 ms
1.3 sec
803 ms
Click here to check amazing Oyis content for Japan. Otherwise, check out these important facts you probably never knew about oyis.org
OYIS is an inclusive school, and we enroll students with diverse interests, creative talents, and service-oriented ideals, who benefit both from the programs we offer and the opportunity to achieve th...
Visit oyis.orgWe analyzed Oyis.org page load time and found that the first response time was 66 ms and then it took 2.1 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.
oyis.org performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value8.5 s
1/100
25%
Value7.7 s
24/100
10%
Value880 ms
32/100
30%
Value0
100/100
15%
Value15.1 s
7/100
10%
66 ms
113 ms
26 ms
33 ms
25 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 80% of them (111 requests) were addressed to the original Oyis.org, 15% (21 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (602 ms) belongs to the original domain Oyis.org.
Page size can be reduced by 405.7 kB (48%)
853.9 kB
448.2 kB
In fact, the total size of Oyis.org main page is 853.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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. HTML takes 554.5 kB which makes up the majority of the site volume.
Potential reduce by 405.0 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 405.0 kB or 73% of the original size.
Potential reduce by 17 B
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 639 B
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. Oyis.org has all CSS files already compressed.
Number of requests can be reduced by 104 (90%)
115
11
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oyis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 67 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.
oyis.org
66 ms
oyis.org
113 ms
theme.min.css
26 ms
custom-frontend-lite.min.css
33 ms
general.min.css
25 ms
eael-8582.css
42 ms
give.css
38 ms
give-donation-summary.css
31 ms
etn-icon.css
47 ms
event-manager-public-styles.css
42 ms
buttons.min.css
47 ms
dashicons.min.css
48 ms
mediaelementplayer-legacy.min.css
52 ms
wp-mediaelement.min.css
55 ms
media-views.min.css
63 ms
imgareaselect.css
54 ms
etn-public.css
60 ms
style.min.css
66 ms
header-footer.min.css
67 ms
post-6820.css
65 ms
eael-27804.css
67 ms
swiper.min.css
72 ms
custom-pro-frontend-lite.min.css
78 ms
all.min.css
74 ms
v4-shims.min.css
80 ms
global.css
84 ms
post-27804.css
86 ms
swiper-bundle.min.css
87 ms
post-8075.css
88 ms
post-8582.css
94 ms
post-78600.css
91 ms
css
47 ms
jquery.min.js
104 ms
jquery-migrate.min.js
102 ms
utils.min.js
102 ms
moxie.min.js
116 ms
plupload.min.js
115 ms
etn-public.js
123 ms
js
102 ms
js
85 ms
34 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
64 ms
custom-pro-widget-nav-menu.min.css
107 ms
widget-theme-elements.min.css
104 ms
widget-posts.min.css
104 ms
animations.min.css
98 ms
eael-77061.css
97 ms
post-77061.css
91 ms
eael-44134.css
89 ms
post-44134.css
97 ms
post-17768.css
91 ms
etn-location.js
95 ms
etn-rsvp.js
93 ms
v4-shims.min.js
93 ms
swiper-bundle.min.js
93 ms
email-decode.min.js
88 ms
general.min.js
351 ms
give-stripe.js
345 ms
hooks.min.js
347 ms
i18n.min.js
346 ms
give.js
345 ms
give-donation-summary.js
343 ms
i18n-loader.js
340 ms
event-manager-public.js
336 ms
underscore.min.js
336 ms
shortcode.min.js
333 ms
backbone.min.js
331 ms
wp-util.min.js
333 ms
wp-backbone.min.js
331 ms
media-models.min.js
332 ms
wp-plupload.min.js
321 ms
core.min.js
318 ms
mouse.min.js
322 ms
sortable.min.js
310 ms
mediaelement-and-player.min.js
303 ms
mediaelement-migrate.min.js
303 ms
wp-mediaelement.min.js
302 ms
api-request.min.js
303 ms
dom-ready.min.js
302 ms
a11y.min.js
304 ms
clipboard.min.js
302 ms
media-views.min.js
304 ms
media-editor.min.js
302 ms
media-audiovideo.min.js
302 ms
hello-frontend.min.js
297 ms
eael-27804.js
295 ms
smush-lazy-load.min.js
295 ms
jquery.sticky.min.js
294 ms
jquery.smartmenus.min.js
295 ms
imagesloaded.min.js
293 ms
gtm.js
273 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhcMWkANDM.ttf
166 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhrsWkANDM.ttf
250 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsSkANDM.ttf
262 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWkANDM.ttf
264 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhHMWkANDM.ttf
265 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduh8MKkANDM.ttf
264 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhycKkANDM.ttf
265 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhrsKkANDM.ttf
263 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhh8KkANDM.ttf
263 ms
eael-77061.js
165 ms
eael-44134.js
128 ms
webpack-pro.runtime.min.js
127 ms
webpack.runtime.min.js
127 ms
frontend-modules.min.js
127 ms
frontend.min.js
138 ms
waypoints.min.js
125 ms
frontend.min.js
172 ms
elements-handlers.min.js
170 ms
elementor.js
141 ms
moment.min.js
172 ms
react.min.js
170 ms
react-dom.min.js
169 ms
escape-html.min.js
173 ms
element.min.js
172 ms
index-calendar.js
198 ms
elementor.js
171 ms
ymca-logo.png
172 ms
website-header-home-scaled.jpg
170 ms
DSC0539-1-scaled.jpg
171 ms
IMG_9163-1-scaled.jpg
170 ms
DSC0289-1-copy-scaled.jpg
208 ms
DSC0972-scaled.jpg
208 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
117 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
116 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
116 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
116 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
117 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
116 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
144 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf
143 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf
144 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
145 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf
145 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf
144 ms
c-60_-1-768x768.png
268 ms
p-1-768x768.png
602 ms
smush-lazyloader-2.gif
100 ms
oyis.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
oyis.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
oyis.org SEO score
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 Oyis.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 Oyis.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.
oyis.org
Open Graph description is not detected on the main page of Oyis. 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: