Tools & Wizards About Us
antic.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

antic.com

WordPress › Setup Configuration File

Page Load Speed

5.8 sec in total

First Response

1.2 sec

Resources Loaded

3.4 sec

Page Rendered

1.2 sec

antic.com screenshot

About Website

Click here to check amazing Antic content. Otherwise, check out these important facts you probably never knew about antic.com

Visit antic.com

Key Findings

We analyzed Antic.com page load time and found that the first response time was 1.2 sec and then it took 4.6 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

antic.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value7.1 s

51/100

10%

Network Requests Diagram

antic.com

1223 ms

style.min.css

114 ms

theme.min.css

227 ms

header-footer.min.css

335 ms

frontend-lite.min.css

345 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 79% of them (45 requests) were addressed to the original Antic.com, 16% (9 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Assets.calendly.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Antic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 159.3 kB (14%)

Content Size

1.1 MB

After Optimization

968.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 122.5 kB

  • Original 153.7 kB
  • After minification 149.5 kB
  • After compression 31.2 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 122.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 749.5 kB
  • After minification 749.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. Antic images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 134 B

  • Original 138.5 kB
  • After minification 138.5 kB
  • After compression 138.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. This website has mostly compressed JavaScripts.

CSS Optimization

-43%

Potential reduce by 36.7 kB

  • Original 86.3 kB
  • After minification 85.5 kB
  • After compression 49.6 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. Antic.com needs all CSS files to be minified and compressed as it can save up to 36.7 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (85%)

Requests Now

47

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

antic.com

antic.com

1223 ms

style.min.css

style.min.css

114 ms

theme.min.css

theme.min.css

227 ms

header-footer.min.css

header-footer.min.css

335 ms

frontend-lite.min.css

frontend-lite.min.css

345 ms

post-8.css

post-8.css

351 ms

swiper.min.css

swiper.min.css

353 ms

frontend-lite.min.css

frontend-lite.min.css

352 ms

post-45.css

post-45.css

348 ms

post-29.css

post-29.css

448 ms

post-23.css

post-23.css

457 ms

post-14.css

post-14.css

464 ms

css

css

34 ms

widget-icon-list.min.css

widget-icon-list.min.css

462 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

485 ms

widget-animated-headline.min.css

widget-animated-headline.min.css

486 ms

widget-icon-box.min.css

widget-icon-box.min.css

560 ms

widget-posts.min.css

widget-posts.min.css

568 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

576 ms

widget.css

widget.css

235 ms

widget.js

widget.js

284 ms

post-251.css

post-251.css

577 ms

animations.min.css

animations.min.css

580 ms

hello-frontend.min.js

hello-frontend.min.js

682 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

682 ms

jquery.min.js

jquery.min.js

687 ms

jquery-migrate.min.js

jquery-migrate.min.js

696 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

698 ms

imagesloaded.min.js

imagesloaded.min.js

700 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

700 ms

webpack.runtime.min.js

webpack.runtime.min.js

786 ms

frontend-modules.min.js

frontend-modules.min.js

800 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

809 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

811 ms

wp-polyfill.min.js

wp-polyfill.min.js

816 ms

hooks.min.js

hooks.min.js

818 ms

i18n.min.js

i18n.min.js

900 ms

frontend.min.js

frontend.min.js

915 ms

waypoints.min.js

waypoints.min.js

926 ms

core.min.js

core.min.js

929 ms

frontend.min.js

frontend.min.js

830 ms

elements-handlers.min.js

elements-handlers.min.js

719 ms

jquery.sticky.min.js

jquery.sticky.min.js

687 ms

slide_wall_content-e1712242905469.jpg

slide_wall_content-e1712242905469.jpg

674 ms

DJI_0021-scaled.jpg

DJI_0021-scaled.jpg

1016 ms

jean-philippe-delberghe-75xPHEQBmvA-unsplash-scaled.jpg

jean-philippe-delberghe-75xPHEQBmvA-unsplash-scaled.jpg

798 ms

cropped-cropped-cropped-Anticom-logo-03-1-180x60-1-e1712239195296.jpg

cropped-cropped-cropped-Anticom-logo-03-1-180x60-1-e1712239195296.jpg

369 ms

website_slider_aantic_financebookshelf-e1712243079572.jpg

website_slider_aantic_financebookshelf-e1712243079572.jpg

713 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

20 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

33 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

57 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

72 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

70 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

69 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

71 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

71 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

71 ms

Accessibility Review

antic.com accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

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

antic.com SEO score

77

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

antic.com

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