Tools & Wizards About Us
warrantee.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

warrantee.com

Warrantee – CONNECT THE WORLD WITH SAFETY. – - Warrantee

Page Load Speed

6.2 sec in total

First Response

365 ms

Resources Loaded

5.4 sec

Page Rendered

382 ms

warrantee.com screenshot

About Website

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

We have patented and operate the The free-insurance model by sponsorship fees from companies. Users (individuals, corporations, medical institutions, etc.) medical institutions, etc.

Visit warrantee.com

Key Findings

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

Performance Metrics

warrantee.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

warrantee.com

365 ms

warrantee.com

2106 ms

js

105 ms

wp-emoji-release.min.js

184 ms

style.min.css

358 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 86% of them (67 requests) were addressed to the original Warrantee.com, 8% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Warrantee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 458.1 kB (32%)

Content Size

1.4 MB

After Optimization

972.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Warrantee.com main page is 1.4 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. 55% of websites need less resources to load. Images take 899.3 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 128.4 kB

  • Original 148.3 kB
  • After minification 144.1 kB
  • After compression 19.8 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 128.4 kB or 87% of the original size.

Image Optimization

-28%

Potential reduce by 252.5 kB

  • Original 899.3 kB
  • After minification 646.8 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, Warrantee needs image optimization as it can save up to 252.5 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 30.8 kB

  • Original 183.1 kB
  • After minification 183.1 kB
  • After compression 152.3 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 30.8 kB or 17% of the original size.

CSS Optimization

-23%

Potential reduce by 46.4 kB

  • Original 200.2 kB
  • After minification 200.2 kB
  • After compression 153.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. Warrantee.com needs all CSS files to be minified and compressed as it can save up to 46.4 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (87%)

Requests Now

68

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

warrantee.com

warrantee.com

365 ms

warrantee.com

warrantee.com

2106 ms

js

js

105 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

184 ms

style.min.css

style.min.css

358 ms

jquery.qtip.min.css

jquery.qtip.min.css

523 ms

directory.min.css

directory.min.css

524 ms

style.min.css

style.min.css

529 ms

theme.min.css

theme.min.css

541 ms

frontend-lite.min.css

frontend-lite.min.css

718 ms

post-755.css

post-755.css

539 ms

elementor-icons.min.css

elementor-icons.min.css

694 ms

frontend-lite.min.css

frontend-lite.min.css

696 ms

uael-frontend.min.css

uael-frontend.min.css

884 ms

all.min.css

all.min.css

920 ms

v4-shims.min.css

v4-shims.min.css

715 ms

post-33.css

post-33.css

868 ms

post-145.css

post-145.css

865 ms

post-204.css

post-204.css

924 ms

ecs-style.css

ecs-style.css

926 ms

post-457.css

post-457.css

1037 ms

post-1238.css

post-1238.css

1038 ms

post-3538.css

post-3538.css

1054 ms

post-3814.css

post-3814.css

1064 ms

post-3819.css

post-3819.css

1065 ms

post-3822.css

post-3822.css

1067 ms

post-3825.css

post-3825.css

1209 ms

css

css

36 ms

fontawesome.min.css

fontawesome.min.css

1378 ms

solid.min.css

solid.min.css

1226 ms

jquery.min.js

jquery.min.js

1414 ms

jquery-migrate.min.js

jquery-migrate.min.js

1239 ms

jquery.qtip.min.js

jquery.qtip.min.js

1244 ms

jquery.directory.min.js

jquery.directory.min.js

1391 ms

v4-shims.min.js

v4-shims.min.js

1396 ms

ecs_ajax_pagination.js

ecs_ajax_pagination.js

1439 ms

ecs.js

ecs.js

1440 ms

widget-icon-list.min.css

widget-icon-list.min.css

1548 ms

widget-posts.min.css

widget-posts.min.css

1549 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

1564 ms

js

js

73 ms

analytics.js

analytics.js

26 ms

collect

collect

17 ms

language-switcher.min.css

language-switcher.min.css

1435 ms

regular.min.css

regular.min.css

1258 ms

script.min.js

script.min.js

1097 ms

hello-frontend.min.js

hello-frontend.min.js

1201 ms

uael-nav-menu.min.js

uael-nav-menu.min.js

1199 ms

jquery_resize.min.js

jquery_resize.min.js

1204 ms

js_cookie.min.js

js_cookie.min.js

1234 ms

imagesloaded.min.js

imagesloaded.min.js

1075 ms

webpack.runtime.min.js

webpack.runtime.min.js

1081 ms

frontend-modules.min.js

frontend-modules.min.js

1180 ms

waypoints.min.js

waypoints.min.js

1176 ms

core.min.js

core.min.js

1046 ms

frontend.min.js

frontend.min.js

1076 ms

ecspro.js

ecspro.js

1031 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1025 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1139 ms

wp-polyfill.min.js

wp-polyfill.min.js

1173 ms

hooks.min.js

hooks.min.js

1072 ms

i18n.min.js

i18n.min.js

1082 ms

frontend.min.js

frontend.min.js

1071 ms

elements-handlers.min.js

elements-handlers.min.js

1063 ms

logo_warrantee.svg

logo_warrantee.svg

781 ms

1b2afa8cbfb57d6ab61443f9f38a39d4.png

1b2afa8cbfb57d6ab61443f9f38a39d4.png

1156 ms

a3a93f26ac915164737032b5159fa6d5.png

a3a93f26ac915164737032b5159fa6d5.png

1505 ms

logo_wht.svg

logo_wht.svg

840 ms

footer.svg

footer.svg

843 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

18 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

21 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

27 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

30 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

34 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

34 ms

fa-solid-900.woff

fa-solid-900.woff

1010 ms

fa-regular-400.woff

fa-regular-400.woff

940 ms

admin-ajax.php

admin-ajax.php

661 ms

Accessibility Review

warrantee.com accessibility score

87

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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.

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

Links do not have a discernible name

Best Practices

warrantee.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

warrantee.com SEO score

89

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

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

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 Warrantee.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 Warrantee.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

warrantee.com

Open Graph data is detected on the main page of Warrantee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: