Tools & Wizards About Us

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

apex.insure

APEX - Insurance, Reinsurance Brokerage and Consultancy services

Page Load Speed

6.3 sec in total

First Response

228 ms

Resources Loaded

5.9 sec

Page Rendered

129 ms

About Website

Welcome to apex.insure homepage info - get ready to check APEX best content right away, or after learning these important things about apex.insure

At APEX, we aspire to provide our clients with more than just exceptional reinsurance brokerage and consultancy services, APEX delivers intelligent, comprehensive reinsurance, risk management, and con...

Visit apex.insure

Key Findings

We analyzed Apex.insure page load time and found that the first response time was 228 ms and then it took 6.1 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

apex.insure performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value10.3 s

24/100

10%

Network Requests Diagram

apex.insure

228 ms

apexib.com

3234 ms

www.apexib.com

787 ms

js

61 ms

font-awesome.min.css

231 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Apex.insure, 81% (26 requests) were made to Apexib.com and 9% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Apexib.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 557.4 kB (45%)

Content Size

1.3 MB

After Optimization

694.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Apex.insure main page is 1.3 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. 35% of websites need less resources to load. Images take 693.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 88.3 kB

  • Original 120.0 kB
  • After minification 107.8 kB
  • After compression 31.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 88.3 kB or 74% of the original size.

Image Optimization

-17%

Potential reduce by 120.6 kB

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

JavaScript Optimization

-69%

Potential reduce by 109.1 kB

  • Original 158.8 kB
  • After minification 151.2 kB
  • After compression 49.7 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 109.1 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 239.3 kB

  • Original 279.3 kB
  • After minification 249.5 kB
  • After compression 39.9 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. Apex.insure needs all CSS files to be minified and compressed as it can save up to 239.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (44%)

Requests Now

25

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

apex.insure accessibility score

63

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

apex.insure best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

apex.insure SEO score

90

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Apex.insure 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 Apex.insure 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

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