Tools & Wizards About Us
innzes.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

innzes.com

Innzes Solutions

Page Load Speed

5.7 sec in total

First Response

1.3 sec

Resources Loaded

3.2 sec

Page Rendered

1.3 sec

innzes.com screenshot

About Website

Welcome to innzes.com homepage info - get ready to check Innzes best content right away, or after learning these important things about innzes.com

Visit innzes.com

Key Findings

We analyzed Innzes.com page load time and found that the first response time was 1.3 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

innzes.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

www.innzes.com

1279 ms

custom-color-overrides.css

187 ms

styles.css

258 ms

style.css

194 ms

style.css

276 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 84% of them (83 requests) were addressed to the original Innzes.com, 10% (10 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Threebeavers.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Innzes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 572.2 kB (19%)

Content Size

3.0 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Innzes.com main page is 3.0 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. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 151.6 kB

  • Original 254.1 kB
  • After minification 247.9 kB
  • After compression 102.5 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 151.6 kB or 60% of the original size.

Image Optimization

-13%

Potential reduce by 281.8 kB

  • Original 2.2 MB
  • After minification 1.9 MB

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, Innzes needs image optimization as it can save up to 281.8 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-22%

Potential reduce by 59.9 kB

  • Original 270.3 kB
  • After minification 270.2 kB
  • After compression 210.4 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 59.9 kB or 22% of the original size.

CSS Optimization

-30%

Potential reduce by 78.9 kB

  • Original 258.8 kB
  • After minification 258.7 kB
  • After compression 179.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. Innzes.com needs all CSS files to be minified and compressed as it can save up to 78.9 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (78%)

Requests Now

86

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Innzes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.innzes.com

www.innzes.com

1279 ms

custom-color-overrides.css

custom-color-overrides.css

187 ms

styles.css

styles.css

258 ms

style.css

style.css

194 ms

style.css

style.css

276 ms

ekiticons.css

ekiticons.css

267 ms

frontend.min.css

frontend.min.css

200 ms

general.min.css

general.min.css

206 ms

eael-29.css

eael-29.css

258 ms

swiper.min.css

swiper.min.css

284 ms

e-swiper.min.css

e-swiper.min.css

282 ms

post-16.css

post-16.css

322 ms

font-awesome.min.css

font-awesome.min.css

326 ms

animate.css

animate.css

337 ms

style.css

style.css

333 ms

responsive.css

responsive.css

346 ms

global.css

global.css

348 ms

widget-text-editor.min.css

widget-text-editor.min.css

388 ms

widget-heading.min.css

widget-heading.min.css

391 ms

widget-icon-list.min.css

widget-icon-list.min.css

400 ms

widget-icon-box.min.css

widget-icon-box.min.css

403 ms

widget-image.min.css

widget-image.min.css

411 ms

post-29.css

post-29.css

416 ms

nav.css

nav.css

454 ms

widget-styles.css

widget-styles.css

531 ms

responsive.css

responsive.css

489 ms

all.min.css

all.min.css

475 ms

v4-shims.min.css

v4-shims.min.css

486 ms

style.min.css

style.min.css

492 ms

font-awesome.min.css

font-awesome.min.css

520 ms

css

css

37 ms

jquery.min.js

jquery.min.js

602 ms

jquery-migrate.min.js

jquery-migrate.min.js

573 ms

v4-shims.min.js

v4-shims.min.js

573 ms

css

css

18 ms

owl.carousel.css

owl.carousel.css

467 ms

sa-owl-theme.css

sa-owl-theme.css

481 ms

animate.min.css

animate.min.css

496 ms

lightgallery.css

lightgallery.css

616 ms

lightgallery-bundle.min.css

lightgallery-bundle.min.css

601 ms

hooks.min.js

hooks.min.js

539 ms

i18n.min.js

i18n.min.js

533 ms

index.js

index.js

529 ms

index.js

index.js

481 ms

responsive-embeds.js

responsive-embeds.js

477 ms

frontend-script.js

frontend-script.js

465 ms

widget-scripts.js

widget-scripts.js

553 ms

general.min.js

general.min.js

453 ms

eael-29.js

eael-29.js

491 ms

nav.js

nav.js

454 ms

happy-addons.min.js

happy-addons.min.js

507 ms

owl.carousel.min.js

owl.carousel.min.js

442 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

496 ms

owl.carousel2.thumbs.min.js

owl.carousel2.thumbs.min.js

489 ms

lightgallery.min.js

lightgallery.min.js

486 ms

lg-video.min.js

lg-video.min.js

454 ms

lg-zoom.min.js

lg-zoom.min.js

555 ms

lg-autoplay.min.js

lg-autoplay.min.js

561 ms

player.min.js

player.min.js

556 ms

webpack.runtime.min.js

webpack.runtime.min.js

549 ms

frontend-modules.min.js

frontend-modules.min.js

542 ms

core.min.js

core.min.js

504 ms

frontend.min.js

frontend.min.js

479 ms

animate-circle.min.js

animate-circle.min.js

598 ms

elementor.js

elementor.js

597 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

594 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

566 ms

main.js

main.js

515 ms

Mask-group-1.png

Mask-group-1.png

519 ms

Mask-group.png

Mask-group.png

509 ms

Mask-group-1-1.png

Mask-group-1-1.png

510 ms

Mask-group-2.png

Mask-group-2.png

509 ms

image_2023_11_22T10_05_17_967Z.png

image_2023_11_22T10_05_17_967Z.png

433 ms

image_2023_11_22T10_05_17_972Z.png

image_2023_11_22T10_05_17_972Z.png

880 ms

port1.png

port1.png

673 ms

port3.png

port3.png

557 ms

port2.png

port2.png

682 ms

Component2.png

Component2.png

546 ms

arrow-right-up.png

arrow-right-up.png

427 ms

Logo.png

Logo.png

491 ms

image-removebg-preview-10-1.png

image-removebg-preview-10-1.png

552 ms

Ellipse-7.png

Ellipse-7.png

555 ms

shawn-adli.jpg

shawn-adli.jpg

609 ms

Rectangle-9564.png

Rectangle-9564.png

656 ms

arrow-right-up.svg

arrow-right-up.svg

582 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

123 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

166 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

200 ms

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

pxiByp8kv8JHgFVrLFj_Z1xlEw.woff

198 ms

pxiGyp8kv8JHgFVrLPTucHtG.woff

pxiGyp8kv8JHgFVrLPTucHtG.woff

200 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

198 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

198 ms

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

pxiByp8kv8JHgFVrLDD4Z1xlEw.woff

199 ms

pxiByp8kv8JHgFVrLBT5Z1xlEw.woff

pxiByp8kv8JHgFVrLBT5Z1xlEw.woff

200 ms

fa-brands-400.woff

fa-brands-400.woff

561 ms

fa-brands-400.woff

fa-brands-400.woff

591 ms

jizaRExUiTo99u79D0KEww.woff

jizaRExUiTo99u79D0KEww.woff

78 ms

polyfills.js

polyfills.js

432 ms

print.css

print.css

67 ms

Accessibility Review

innzes.com accessibility score

80

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

innzes.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

innzes.com SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Innzes.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 Innzes.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.

Social Sharing Optimization

innzes.com

Open Graph description is not detected on the main page of Innzes. 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: