Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

Page Load Speed

4.2 sec in total

First Response

184 ms

Resources Loaded

3.9 sec

Page Rendered

126 ms

antipoleez.com screenshot

About Website

Visit antipoleez.com now to see the best up-to-date Antipoleez content and also check out these interesting facts you probably never knew about antipoleez.com

AntiPoleez eliminate alcohol breath, get rid of alcohol breath, get rid of onion breath, get rid of garlic breath, get rid of cigarette breath, get rid of bad breath

Visit antipoleez.com

Key Findings

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

Performance Metrics

antipoleez.com performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value6.4 s

59/100

10%

Network Requests Diagram

www.antipoleez.com

184 ms

css-base.css

34 ms

css-element.css

42 ms

css-contents.css

47 ms

css-edits.css

46 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 15% of them (5 requests) were addressed to the original Antipoleez.com, 26% (9 requests) were made to Ep.yimg.com and 21% (7 requests) were made to Lib.store.yahoo.net. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Ep.yimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.2 kB (58%)

Content Size

205.5 kB

After Optimization

86.3 kB

In fact, the total size of Antipoleez.com main page is 205.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 177.3 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 8.2 kB

  • Original 12.5 kB
  • After minification 12.0 kB
  • After compression 4.4 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 8.2 kB or 65% of the original size.

JavaScript Optimization

-56%

Potential reduce by 98.5 kB

  • Original 177.3 kB
  • After minification 177.2 kB
  • After compression 78.8 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 98.5 kB or 56% of the original size.

CSS Optimization

-80%

Potential reduce by 12.6 kB

  • Original 15.8 kB
  • After minification 11.1 kB
  • After compression 3.1 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. Antipoleez.com needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (48%)

Requests Now

25

After Optimization

13

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

Accessibility Review

antipoleez.com accessibility score

78

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

antipoleez.com best practices score

42

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

antipoleez.com SEO score

83

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

High

Document uses plugins

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Antipoleez.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Antipoleez.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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