Tools & Wizards About Us
warrantee.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% 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.6 sec in total

First Response

387 ms

Resources Loaded

5.8 sec

Page Rendered

354 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 387 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

warrantee.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value430 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

warrantee.com

387 ms

warrantee.com

2282 ms

js

89 ms

wp-emoji-release.min.js

192 ms

style.min.css

371 ms

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

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

951.9 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. 60% 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 130.5 kB

  • Original 150.4 kB
  • After minification 146.1 kB
  • After compression 19.9 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 130.5 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

-13%

Potential reduce by 19.4 kB

  • Original 150.7 kB
  • After minification 150.7 kB
  • After compression 131.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 19.4 kB or 13% 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 57 (88%)

Requests Now

65

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 65 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 28 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

387 ms

warrantee.com

warrantee.com

2282 ms

js

js

89 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

192 ms

style.min.css

style.min.css

371 ms

jquery.qtip.min.css

jquery.qtip.min.css

523 ms

directory.min.css

directory.min.css

525 ms

style.min.css

style.min.css

528 ms

theme.min.css

theme.min.css

537 ms

frontend-lite.min.css

frontend-lite.min.css

724 ms

post-755.css

post-755.css

544 ms

elementor-icons.min.css

elementor-icons.min.css

692 ms

frontend-lite.min.css

frontend-lite.min.css

694 ms

uael-frontend.min.css

uael-frontend.min.css

1044 ms

all.min.css

all.min.css

886 ms

v4-shims.min.css

v4-shims.min.css

718 ms

post-33.css

post-33.css

863 ms

post-145.css

post-145.css

864 ms

post-204.css

post-204.css

894 ms

ecs-style.css

ecs-style.css

896 ms

post-457.css

post-457.css

1032 ms

post-1238.css

post-1238.css

1033 ms

post-3538.css

post-3538.css

1074 ms

post-3814.css

post-3814.css

1075 ms

post-3819.css

post-3819.css

1076 ms

post-3822.css

post-3822.css

1202 ms

post-3825.css

post-3825.css

1201 ms

css

css

42 ms

fontawesome.min.css

fontawesome.min.css

1214 ms

solid.min.css

solid.min.css

1236 ms

jquery.min.js

jquery.min.js

1416 ms

jquery-migrate.min.js

jquery-migrate.min.js

1250 ms

jquery.qtip.min.js

jquery.qtip.min.js

1540 ms

jquery.directory.min.js

jquery.directory.min.js

1370 ms

v4-shims.min.js

v4-shims.min.js

1386 ms

ecs_ajax_pagination.js

ecs_ajax_pagination.js

1412 ms

ecs.js

ecs.js

1430 ms

widget-icon-list.min.css

widget-icon-list.min.css

1565 ms

widget-posts.min.css

widget-posts.min.css

1564 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

1583 ms

language-switcher.min.css

language-switcher.min.css

1439 ms

regular.min.css

regular.min.css

1288 ms

script.min.js

script.min.js

1194 ms

hello-frontend.min.js

hello-frontend.min.js

1194 ms

uael-nav-menu.min.js

uael-nav-menu.min.js

1210 ms

jquery_resize.min.js

jquery_resize.min.js

1233 ms

js_cookie.min.js

js_cookie.min.js

1228 ms

imagesloaded.min.js

imagesloaded.min.js

1144 ms

webpack.runtime.min.js

webpack.runtime.min.js

1192 ms

frontend-modules.min.js

frontend-modules.min.js

1166 ms

waypoints.min.js

waypoints.min.js

1182 ms

core.min.js

core.min.js

1080 ms

frontend.min.js

frontend.min.js

1082 ms

ecspro.js

ecspro.js

1126 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1161 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1160 ms

wp-polyfill.min.js

wp-polyfill.min.js

1050 ms

hooks.min.js

hooks.min.js

1087 ms

i18n.min.js

i18n.min.js

1048 ms

frontend.min.js

frontend.min.js

1116 ms

elements-handlers.min.js

elements-handlers.min.js

1153 ms

logo_warrantee.svg

logo_warrantee.svg

667 ms

1b2afa8cbfb57d6ab61443f9f38a39d4.png

1b2afa8cbfb57d6ab61443f9f38a39d4.png

866 ms

a3a93f26ac915164737032b5159fa6d5.png

a3a93f26ac915164737032b5159fa6d5.png

1609 ms

logo_wht.svg

logo_wht.svg

738 ms

footer.svg

footer.svg

809 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

53 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

74 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

106 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

106 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

106 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

105 ms

fa-solid-900.woff

fa-solid-900.woff

1331 ms

fa-regular-400.woff

fa-regular-400.woff

825 ms

admin-ajax.php

admin-ajax.php

587 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: