8.8 sec in total
2 sec
5.9 sec
1 sec
Visit ondistudio.com now to see the best up-to-date Ondi Studio content and also check out these interesting facts you probably never knew about ondistudio.com
Wedding photographers and videographers Toronto. Experienced Videographers and photographers! Booking 2021-2022. Live video streaming available!
Visit ondistudio.comWe analyzed Ondistudio.com page load time and found that the first response time was 2 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ondistudio.com performance score
name
value
score
weighting
Value15.2 s
0/100
10%
Value22.9 s
0/100
25%
Value25.5 s
0/100
10%
Value1,030 ms
26/100
30%
Value0.043
99/100
15%
Value30.7 s
0/100
10%
1964 ms
143 ms
33 ms
94 ms
145 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 89% of them (121 requests) were addressed to the original Ondistudio.com, 8% (11 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ondistudio.com.
Page size can be reduced by 2.9 MB (33%)
8.7 MB
5.9 MB
In fact, the total size of Ondistudio.com main page is 8.7 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. 75% 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. Images take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 154.3 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 154.3 kB or 84% of the original size.
Potential reduce by 146.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. Ondi Studio images are well optimized though.
Potential reduce by 948.7 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 948.7 kB or 70% of the original size.
Potential reduce by 1.6 MB
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. Ondistudio.com needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 86% of the original size.
Number of requests can be reduced by 99 (83%)
119
20
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ondi Studio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 60 to 1 for JavaScripts and from 41 to 1 for CSS and as a result speed up the page load time.
ondistudio.com
1964 ms
style.min.css
143 ms
css
33 ms
menu-animation.min.css
94 ms
blocks.style.build.css
145 ms
styles.css
73 ms
contact-form-7-main.min.css
89 ms
embedpress.css
132 ms
ftg.css
121 ms
font-awesome.css
31 ms
justifiedGallery.min.css
122 ms
slick.css
136 ms
twentytwenty.css
145 ms
ep-elements.css
149 ms
ep-tables.css
163 ms
ep-sticky-videos.css
156 ms
ep-heading.css
165 ms
ep-pricing-list.css
171 ms
header-footer-elementor.css
185 ms
frontend.min.css
292 ms
general.min.css
197 ms
eael-440.css
230 ms
elementor-icons.min.css
206 ms
swiper.min.css
208 ms
post-444.css
223 ms
embedpress-elementor.css
235 ms
frontend.min.css
473 ms
post-440.css
251 ms
frontend.css
324 ms
post-2961.css
277 ms
style.css
270 ms
ekiticons.css
349 ms
dashicons.min.css
354 ms
plyr.css
337 ms
widget-styles.css
454 ms
responsive.css
424 ms
css
18 ms
fontawesome.min.css
415 ms
brands.min.css
387 ms
galleries.min.css
382 ms
all.min.css
400 ms
v4-shims.min.css
362 ms
jquery.min.js
417 ms
jquery-migrate.min.js
392 ms
plyr.polyfilled.js
418 ms
style.min.js
396 ms
index.js
376 ms
index.js
383 ms
pdfobject.min.js
383 ms
initplyr.js
483 ms
front.js
487 ms
vimeo-player.js
479 ms
wp-polyfill-inert.min.js
472 ms
regenerator-runtime.min.js
470 ms
wp-polyfill.min.js
465 ms
react.min.js
449 ms
hooks.min.js
505 ms
deprecated.min.js
493 ms
dom.min.js
493 ms
react-dom.min.js
550 ms
escape-html.min.js
471 ms
element.min.js
465 ms
is-shallow-equal.min.js
518 ms
i18n.min.js
501 ms
keycodes.min.js
464 ms
priority-queue.min.js
474 ms
compose.min.js
446 ms
private-apis.min.js
456 ms
redux-routine.min.js
442 ms
data.min.js
440 ms
ads.js
419 ms
documents-viewer-script.js
407 ms
jquery.finalTilesGallery.js
393 ms
gtm4wp-form-move-tracker.js
389 ms
jquery.justifiedGallery.min.js
396 ms
jquery.fitvids.js
376 ms
jquery.matchHeight.js
363 ms
slick.min.js
360 ms
imagesloaded.pkgd.min.js
365 ms
jquery.event.move.js
356 ms
jquery.twentytwenty.js
353 ms
ep-sticky-videos.js
354 ms
ep-scripts.js
415 ms
general.min.js
380 ms
gtm.js
177 ms
eael-440.js
276 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
28 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
42 ms
wXKrE3kQtZQ4pF3D51jcBQ.ttf
73 ms
wXKuE3kQtZQ4pF3D7-P5FeMKnQ.ttf
112 ms
KtkpALCRZonmalTgyPmRfsWl42Q.ttf
145 ms
Ktk0ALCRZonmalTgyPmRfs1WwHTQN4M.ttf
112 ms
Ktk0ALCRZonmalTgyPmRfs0OwXTQN4M.ttf
110 ms
Ktk0ALCRZonmalTgyPmRfs1qwnTQN4M.ttf
112 ms
Ktk0ALCRZonmalTgyPmRfs16x3TQN4M.ttf
111 ms
Ktk0ALCRZonmalTgyPmRfs0exnTQN4M.ttf
251 ms
Ktk0ALCRZonmalTgyPmRfs0CxXTQN4M.ttf
143 ms
frontend-script.js
274 ms
widget-scripts.js
282 ms
v4-shims.min.js
275 ms
webpack-pro.runtime.min.js
288 ms
webpack.runtime.min.js
313 ms
frontend-modules.min.js
341 ms
frontend.min.js
298 ms
waypoints.min.js
255 ms
core.min.js
259 ms
frontend.min.js
280 ms
elements-handlers.min.js
290 ms
animate-circle.min.js
258 ms
elementor.js
233 ms
underscore.min.js
247 ms
wp-util.min.js
242 ms
frontend.min.js
259 ms
fa-solid-900.woff
316 ms
fa-regular-400.woff
257 ms
eicons.woff
330 ms
fa-brands-400.woff
344 ms
astra.woff
269 ms
TDL-Pattern-02.jpg
299 ms
cropped-ondistudio_logo-1-1-283x77.png
299 ms
DSC_1065.jpg
388 ms
5B4A9840.jpg
719 ms
OND09226-scaled-1.jpg
341 ms
8_96.jpg
571 ms
bg2.jpg
395 ms
5B4A9849-768x1152.jpg
362 ms
os20-768x1151.jpg
357 ms
bride-1-2-768x1152.jpg
391 ms
liam-2-768x1152.jpg
396 ms
DSC_7710.jpg
496 ms
wedding-wire-ondistudio.png
454 ms
es-member-badge-2021.png
402 ms
WL_Wedluxe-Mag-Badge-2021_Black.png
497 ms
Best-Wedding-Photographer-Toronto-badge.png
593 ms
Best-Wedding-Videographer-Toronto-badge-768x625.png
491 ms
Ondi-Studio-black-low-res-3-300x85.png
516 ms
ondistudio.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[role]s are not contained by their required parent element
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
ondistudio.com 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
ondistudio.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ondistudio.com 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 Ondistudio.com 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.
ondistudio.com
Open Graph data is detected on the main page of Ondi Studio. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: