Tools & Wizards About Us
exaxe.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

exaxe.com

Page Load Speed

6.2 sec in total

First Response

1.6 sec

Resources Loaded

4.4 sec

Page Rendered

273 ms

exaxe.com screenshot

About Website

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

DELIVERING TOMORROW’S SOLUTIONS TODAY Exaxe is a specialist solution provider that helps life, pensions, and wealth companies launch new products faster, adm

Visit exaxe.com

Key Findings

We analyzed Exaxe.com page load time and found that the first response time was 1.6 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

exaxe.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value14.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.7 s

0/100

25%

SI (Speed Index)

Value27.2 s

0/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.096

90/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

www.exaxe.com

1559 ms

wp-emoji-release.min.js

185 ms

styles.css

189 ms

normalize.css

190 ms

style.css

196 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 70% of them (65 requests) were addressed to the original Exaxe.com, 5% (5 requests) were made to Use.typekit.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Exaxe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 631.0 kB (53%)

Content Size

1.2 MB

After Optimization

570.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Exaxe.com main page is 1.2 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. 50% of websites need less resources to load. Javascripts take 579.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 60.5 kB

  • Original 73.2 kB
  • After minification 72.0 kB
  • After compression 12.7 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 60.5 kB or 83% of the original size.

Image Optimization

-11%

Potential reduce by 45.2 kB

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

JavaScript Optimization

-68%

Potential reduce by 394.6 kB

  • Original 579.6 kB
  • After minification 572.8 kB
  • After compression 185.1 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 394.6 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 130.8 kB

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

Requests Breakdown

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

Requests Now

86

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.exaxe.com

www.exaxe.com

1559 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

185 ms

styles.css

styles.css

189 ms

normalize.css

normalize.css

190 ms

style.css

style.css

196 ms

form-basic.min.css

form-basic.min.css

195 ms

ubermenu.min.css

ubermenu.min.css

404 ms

blackwhite2.css

blackwhite2.css

407 ms

cleanwhite.css

cleanwhite.css

405 ms

font-awesome.min.css

font-awesome.min.css

407 ms

conditionizr-4.3.0.min.js

conditionizr-4.3.0.min.js

419 ms

jquery.js

jquery.js

597 ms

jquery-migrate.min.js

jquery-migrate.min.js

512 ms

scripts.js

scripts.js

494 ms

jquery.easing.min.js

jquery.easing.min.js

6 ms

jzj6lwl.js

jzj6lwl.js

197 ms

buttons.js

buttons.js

10 ms

slides.min.jquery.js

slides.min.jquery.js

512 ms

jquery.bxslider.css

jquery.bxslider.css

449 ms

styles.css

styles.css

451 ms

modernizr-2.7.1.min.js

modernizr-2.7.1.min.js

522 ms

comment-reply.min.js

comment-reply.min.js

578 ms

jquery.form.min.js

jquery.form.min.js

580 ms

scripts.js

scripts.js

579 ms

TweenMax.min.js

TweenMax.min.js

813 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

636 ms

wporigo_ssp.js

wporigo_ssp.js

635 ms

js

js

23 ms

ubermenu.min.js

ubermenu.min.js

720 ms

wp-embed.min.js

wp-embed.min.js

721 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

721 ms

carousel.js

carousel.js

727 ms

3

3

185 ms

main-bg.jpg

main-bg.jpg

487 ms

exaxe_white.png

exaxe_white.png

138 ms

provider-of-the-year.png

provider-of-the-year.png

140 ms

Illustrateplus2015-Height-28-pix.png

Illustrateplus2015-Height-28-pix.png

141 ms

adminplus2015-Height-28-pix.png

adminplus2015-Height-28-pix.png

140 ms

channelplus2015-height-28-pix.png

channelplus2015-height-28-pix.png

468 ms

ageas.png

ageas.png

473 ms

AXALifeInvestBW2120X45.jpg

AXALifeInvestBW2120X45.jpg

473 ms

aviva.png

aviva.png

471 ms

capita.png

capita.png

469 ms

eureko.png

eureko.png

474 ms

interamerican.png

interamerican.png

475 ms

liberata.png

liberata.png

478 ms

Police-Mutual-Black-and-White-120x45.png

Police-Mutual-Black-and-White-120x45.png

476 ms

prudential.png

prudential.png

476 ms

Retirement-Advantage-Black-and-White-120x451.png

Retirement-Advantage-Black-and-White-120x451.png

478 ms

rsa.png

rsa.png

479 ms

scottish_mutual.png

scottish_mutual.png

479 ms

scottish_provident.png

scottish_provident.png

480 ms

scottish_widows.png

scottish_widows.png

480 ms

zurich.png

zurich.png

480 ms

UK-2016-Budget-270x105.png

UK-2016-Budget-270x105.png

747 ms

Fin-tech-finalists-270x105.png

Fin-tech-finalists-270x105.png

582 ms

Freedom-nothing-left-lose-270x105.png

Freedom-nothing-left-lose-270x105.png

670 ms

Image-1.-Exaxe-SaaS-Offering-270x105.jpg

Image-1.-Exaxe-SaaS-Offering-270x105.jpg

521 ms

twitter.png

twitter.png

521 ms

facebook.png

facebook.png

555 ms

linkedin.png

linkedin.png

600 ms

googleplus.png

googleplus.png

606 ms

rss.png

rss.png

648 ms

fps_bg.png

fps_bg.png

657 ms

the_arrow.png

the_arrow.png

677 ms

PBFve8FCn2NJzkkXlGAPzvMe2fGJgXN3IQydZXQtx0MffV_VMUMmeMI6MK6f5Mw.eot

PBFve8FCn2NJzkkXlGAPzvMe2fGJgXN3IQydZXQtx0MffV_VMUMmeMI6MK6f5Mw.eot

29 ms

PkBrOQoqXHKP6nALzFhJiGjAUKGgETBbwfLXUbujc43ffJLbMUMmeMI6MK6f5Mq.eot

PkBrOQoqXHKP6nALzFhJiGjAUKGgETBbwfLXUbujc43ffJLbMUMmeMI6MK6f5Mq.eot

111 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

875 ms

count.js

count.js

89 ms

1935861.js

1935861.js

426 ms

analytics.js

analytics.js

256 ms

getAllAppDefault.esi

getAllAppDefault.esi

122 ms

left-arrow.png

left-arrow.png

283 ms

right-arrow.png

right-arrow.png

299 ms

bx_loader.gif

bx_loader.gif

307 ms

controls.png

controls.png

328 ms

0AtT5ZOe6NEK_XNdvSE1pswmSWe3MoWezs08kqJK6ywffJ2bMUMmeMI6MK6f5MI.eot

0AtT5ZOe6NEK_XNdvSE1pswmSWe3MoWezs08kqJK6ywffJ2bMUMmeMI6MK6f5MI.eot

39 ms

collect

collect

22 ms

getSegment.php

getSegment.php

156 ms

checkOAuth.esi

checkOAuth.esi

20 ms

t.dhj

t.dhj

22 ms

t.dhj

t.dhj

20 ms

cm

cm

42 ms

x35248

x35248

124 ms

s-3271.xgi

s-3271.xgi

14 ms

xrefid.xgi

xrefid.xgi

6 ms

pixel

pixel

16 ms

hbpix

hbpix

55 ms

13 ms

6 ms

pixel

pixel

15 ms

2981

2981

28 ms

__ptq.gif

__ptq.gif

6 ms

Accessibility Review

exaxe.com accessibility score

84

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 have valid values

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

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.

Best Practices

exaxe.com best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

exaxe.com SEO score

82

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exaxe.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Exaxe.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

exaxe.com

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