4 sec in total
944 ms
2.7 sec
352 ms
Click here to check amazing Ozog Eye content. Otherwise, check out these important facts you probably never knew about ozogeye.com
Visit ozogeye.comWe analyzed Ozogeye.com page load time and found that the first response time was 944 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ozogeye.com performance score
name
value
score
weighting
Value16.6 s
0/100
10%
Value28.8 s
0/100
25%
Value16.6 s
0/100
10%
Value400 ms
67/100
30%
Value0
100/100
15%
Value28.8 s
0/100
10%
944 ms
120 ms
120 ms
123 ms
92 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 91% of them (125 requests) were addressed to the original Ozogeye.com, 7% (9 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (944 ms) belongs to the original domain Ozogeye.com.
Page size can be reduced by 2.8 MB (42%)
6.7 MB
3.8 MB
In fact, the total size of Ozogeye.com main page is 6.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. 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. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 48.6 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 48.6 kB or 80% of the original size.
Potential reduce by 87.5 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. Ozog Eye images are well optimized though.
Potential reduce by 1.3 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.3 MB or 71% of the original size.
Potential reduce by 1.4 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. Ozogeye.com needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 88% of the original size.
Number of requests can be reduced by 111 (90%)
124
13
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ozog Eye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 96 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
ozogeye.com
944 ms
wp-emoji-release.min.js
120 ms
layerslider.css
120 ms
settings.css
123 ms
mediaelementplayer-legacy.min.css
92 ms
wp-mediaelement.min.css
90 ms
style.css
124 ms
font-awesome.min.css
148 ms
style.min.css
145 ms
style.css
175 ms
dripicons.css
150 ms
stylesheet.min.css
337 ms
print.css
172 ms
style_dynamic.css
177 ms
responsive.min.css
233 ms
style_dynamic_responsive.css
192 ms
js_composer.min.css
311 ms
css
31 ms
ScrollToPlugin.min.js
202 ms
greensock.js
260 ms
jquery.js
249 ms
jquery-migrate.min.js
235 ms
layerslider.kreaturamedia.jquery.js
289 ms
layerslider.transitions.js
262 ms
jquery.themepunch.tools.min.js
441 ms
jquery.themepunch.revolution.min.js
280 ms
mediaelement-and-player.min.js
408 ms
mediaelement-migrate.min.js
408 ms
core.min.js
311 ms
widget.min.js
355 ms
accordion.min.js
355 ms
position.min.js
355 ms
menu.min.js
356 ms
wp-sanitize.min.js
356 ms
wp-a11y.min.js
357 ms
autocomplete.min.js
357 ms
button.min.js
357 ms
datepicker.min.js
358 ms
mouse.min.js
358 ms
resizable.min.js
356 ms
draggable.min.js
355 ms
dialog.min.js
352 ms
droppable.min.js
352 ms
progressbar.min.js
331 ms
selectable.min.js
326 ms
sortable.min.js
326 ms
slider.min.js
313 ms
spinner.min.js
306 ms
tooltip.min.js
304 ms
tabs.min.js
302 ms
effect.min.js
285 ms
effect-blind.min.js
273 ms
effect-bounce.min.js
257 ms
effect-clip.min.js
257 ms
effect-drop.min.js
246 ms
effect-explode.min.js
236 ms
effect-fade.min.js
233 ms
effect-fold.min.js
206 ms
effect-highlight.min.js
206 ms
effect-pulsate.min.js
165 ms
effect-size.min.js
107 ms
effect-scale.min.js
111 ms
effect-shake.min.js
107 ms
effect-slide.min.js
79 ms
effect-transfer.min.js
67 ms
doubletaptogo.js
85 ms
modernizr.min.js
85 ms
jquery.appear.js
87 ms
hoverIntent.min.js
86 ms
counter.js
86 ms
easypiechart.js
146 ms
mixitup.js
146 ms
jquery.prettyPhoto.min.js
300 ms
jquery.fitvids.js
301 ms
jquery.flexslider-min.js
298 ms
wp-mediaelement.min.js
302 ms
infinitescroll.min.js
301 ms
jquery.waitforimages.js
296 ms
jquery.form.min.js
334 ms
waypoints.min.js
337 ms
jplayer.min.js
332 ms
bootstrap.carousel.js
335 ms
skrollr.js
335 ms
Chart.min.js
331 ms
jquery.easing.1.3.js
345 ms
abstractBaseClass.js
345 ms
jquery.countdown.js
345 ms
star.gif
121 ms
jquery.multiscroll.min.js
328 ms
jquery.justifiedGallery.min.js
327 ms
bigtext.js
328 ms
jquery.sticky-kit.min.js
353 ms
owl.carousel.min.js
352 ms
typed.js
356 ms
jquery.carouFredSel-6.2.1.min.js
356 ms
lemmon-slider.min.js
353 ms
jquery.fullPage.min.js
353 ms
jquery.mousewheel.min.js
354 ms
jquery.touchSwipe.min.js
352 ms
isotope.pkgd.min.js
353 ms
packery-mode.pkgd.min.js
351 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
79 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff
81 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
234 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
241 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
242 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
241 ms
jquery.stretch.js
348 ms
imagesloaded.js
332 ms
rangeslider.min.js
359 ms
jquery.event.move.js
360 ms
jquery.twentytwenty.js
359 ms
starV6.gif
163 ms
TweenLite.min.js
301 ms
smoothPageScroll.min.js
303 ms
default_dynamic.js
302 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff
150 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff
153 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
151 ms
default.min.js
178 ms
comment-reply.min.js
176 ms
js_composer_front.min.js
175 ms
qode-like.min.js
174 ms
wp-embed.min.js
188 ms
fontawesome-webfont.woff
233 ms
logo_new2.png
209 ms
logo_new2-mobile.png
209 ms
adorable-baby-babysitter-1257110.jpg
275 ms
icon-1-150x150.png
207 ms
icon-6-150x150.png
207 ms
icon-3-150x150.png
199 ms
icon-4-150x150.png
200 ms
icon-5-150x150.png
198 ms
quote-pic-150x150.png
199 ms
istockphoto-506582554-2048x2048.png
242 ms
istockphoto-898236054-2048x2048.png
241 ms
skin.css
49 ms
ozogeye.com accessibility score
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
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.
ozogeye.com 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
ozogeye.com 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
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 Ozogeye.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 Ozogeye.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.
ozogeye.com
Open Graph description is not detected on the main page of Ozog Eye. 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: