Tools & Wizards About Us
ifrs17explained.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

ifrs17explained.com

IFRS 17 Explained - Understanding the new accounting standard

Page Load Speed

4.4 sec in total

First Response

1.1 sec

Resources Loaded

2.9 sec

Page Rendered

476 ms

ifrs17explained.com screenshot

About Website

Click here to check amazing IFRS 17 Explained content. Otherwise, check out these important facts you probably never knew about ifrs17explained.com

How does the IFRS 17 model work, which disclosures are needed, the timelines and what are the differences and similarities compared to IFRS 4 and Solvency 2

Visit ifrs17explained.com

Key Findings

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

Performance Metrics

ifrs17explained.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

ifrs17explained.com

1111 ms

wp-emoji-release.min.js

92 ms

bootstrap.min.css

182 ms

styles.css

271 ms

ctf-styles.css

272 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 81% of them (38 requests) were addressed to the original Ifrs17explained.com, 4% (2 requests) were made to Platform.twitter.com and 4% (2 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ifrs17explained.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.6 kB (17%)

Content Size

484.3 kB

After Optimization

399.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 57.4 kB

  • Original 69.2 kB
  • After minification 66.3 kB
  • After compression 11.8 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 57.4 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 21.3 kB

  • Original 213.8 kB
  • After minification 192.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. IFRS 17 Explained images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.9 kB

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

CSS Optimization

-5%

Potential reduce by 3.0 kB

  • Original 65.3 kB
  • After minification 65.3 kB
  • After compression 62.3 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. Ifrs17explained.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (68%)

Requests Now

41

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ifrs17explained.com

ifrs17explained.com

1111 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

92 ms

bootstrap.min.css

bootstrap.min.css

182 ms

styles.css

styles.css

271 ms

ctf-styles.css

ctf-styles.css

272 ms

style.css

style.css

361 ms

font-awesome.min.css

font-awesome.min.css

272 ms

elementor-icons.min.css

elementor-icons.min.css

274 ms

animations.min.css

animations.min.css

274 ms

frontend.min.css

frontend.min.css

365 ms

post-203.css

post-203.css

368 ms

jquery.js

jquery.js

369 ms

jquery-migrate.min.js

jquery-migrate.min.js

370 ms

widgets.js

widgets.js

105 ms

slick.min.js

slick.min.js

509 ms

imagesloaded.min.js

imagesloaded.min.js

509 ms

navigation.js

navigation.js

513 ms

scripts.js

scripts.js

508 ms

ctf-scripts.js

ctf-scripts.js

516 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

514 ms

scripts.js

scripts.js

595 ms

custom.min.js

custom.min.js

594 ms

wp-embed.min.js

wp-embed.min.js

632 ms

webfontloader.js

webfontloader.js

632 ms

position.min.js

position.min.js

595 ms

dialog.min.js

dialog.min.js

635 ms

waypoints.min.js

waypoints.min.js

769 ms

swiper.jquery.min.js

swiper.jquery.min.js

773 ms

frontend.min.js

frontend.min.js

773 ms

ZOW0u-Iy_normal.jpg

ZOW0u-Iy_normal.jpg

133 ms

Xpjqk9NZ_normal.jpg

Xpjqk9NZ_normal.jpg

126 ms

Layer-9-2-150x150.jpg

Layer-9-2-150x150.jpg

343 ms

i1-2.png

i1-2.png

332 ms

i2-2.png

i2-2.png

334 ms

i3-2.png

i3-2.png

413 ms

TimeLines-2.png

TimeLines-2.png

445 ms

frontpage-360x360.png

frontpage-360x360.png

521 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

595 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

573 ms

eicons.woff

eicons.woff

472 ms

books-business-computer-459654.jpg

books-business-computer-459654.jpg

83 ms

css

css

46 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNisDp6_dAyM.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNisDp6_dAyM.woff

119 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNisDp6_dAyM.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXNisDp6_dAyM.woff

119 ms

frontend-msie.min.css

frontend-msie.min.css

183 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

77 ms

settings

settings

99 ms

Accessibility Review

ifrs17explained.com accessibility score

94

Accessibility Issues

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

ifrs17explained.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ifrs17explained.com SEO score

85

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

ifrs17explained.com

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