Tools & Wizards About Us
zmessenger.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

zmessenger.com

Digital Marketing Agency | Digital Marketing Agencies in Sri Lanka

Page Load Speed

24.7 sec in total

First Response

1.1 sec

Resources Loaded

23.3 sec

Page Rendered

306 ms

zmessenger.com screenshot

About Website

Click here to check amazing Zmessenger content for Sri Lanka. Otherwise, check out these important facts you probably never knew about zmessenger.com

We are a full spectrum digital Marketing Agency in Sri Lanka delivering exceptional consumer experiences that are digitally led, data driven and multichannel for brands to win the digital experiences ...

Visit zmessenger.com

Key Findings

We analyzed Zmessenger.com page load time and found that the first response time was 1.1 sec and then it took 23.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

zmessenger.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value28.3 s

0/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.164

72/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

www.zmessenger.com

1135 ms

wp-emoji-release.min.js

119 ms

css

65 ms

components.css

217 ms

style.css

392 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 74% of them (48 requests) were addressed to the original Zmessenger.com, 15% (10 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Analytics.adstudio.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 134.8 kB (12%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zmessenger.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 676.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 70.9 kB

  • Original 86.8 kB
  • After minification 82.7 kB
  • After compression 15.9 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 70.9 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 1.4 kB

  • Original 676.5 kB
  • After minification 675.0 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. Zmessenger images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 39.1 kB

  • Original 200.2 kB
  • After minification 200.2 kB
  • After compression 161.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 39.1 kB or 20% of the original size.

CSS Optimization

-13%

Potential reduce by 23.3 kB

  • Original 180.1 kB
  • After minification 175.4 kB
  • After compression 156.8 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. Zmessenger.com needs all CSS files to be minified and compressed as it can save up to 23.3 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (52%)

Requests Now

50

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.zmessenger.com

www.zmessenger.com

1135 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

119 ms

css

css

65 ms

components.css

components.css

217 ms

style.css

style.css

392 ms

styles.css

styles.css

285 ms

settings.css

settings.css

285 ms

socicon.css

socicon.css

305 ms

genericons.css

genericons.css

450 ms

academicons.min.css

academicons.min.css

308 ms

font-awesome.min.css

font-awesome.min.css

382 ms

dashicons.min.css

dashicons.min.css

479 ms

js_composer.min.css

js_composer.min.css

611 ms

jquery.js

jquery.js

450 ms

jquery-migrate.min.js

jquery-migrate.min.js

476 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

492 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

495 ms

js

js

70 ms

css

css

61 ms

animate.min.css

animate.min.css

509 ms

components.js

components.js

780 ms

theme.js

theme.js

564 ms

scripts.js

scripts.js

575 ms

social-icons-widget-frontend.js

social-icons-widget-frontend.js

579 ms

wp-embed.min.js

wp-embed.min.js

723 ms

js_composer_front.min.js

js_composer_front.min.js

730 ms

waypoints.min.js

waypoints.min.js

731 ms

matomo.js

matomo.js

20178 ms

zMessenger-Logo.jpg

zMessenger-Logo.jpg

185 ms

Innovation-Beyond.jpg

Innovation-Beyond.jpg

261 ms

Learn-Unlearn-Relearn..jpg

Learn-Unlearn-Relearn..jpg

648 ms

Reimagine.jpg

Reimagine.jpg

263 ms

Driven-by-Data.jpg

Driven-by-Data.jpg

260 ms

APAC-Awads-Gold-Winner_255x84-1.png

APAC-Awads-Gold-Winner_255x84-1.png

186 ms

SLBestEmployer_255x84.jpg

SLBestEmployer_255x84.jpg

260 ms

NBA.jpg

NBA.jpg

647 ms

SAPS-1_255x84.jpg

SAPS-1_255x84.jpg

646 ms

ZeroOne1_255x84.jpg

ZeroOne1_255x84.jpg

646 ms

ZeroOne2_1_255x84.jpg

ZeroOne2_1_255x84.jpg

644 ms

ZeroOne3_255x84.jpg

ZeroOne3_255x84.jpg

644 ms

ZeroOne4_255x84.jpg

ZeroOne4_255x84.jpg

850 ms

eSwabhimani_255x84.jpg

eSwabhimani_255x84.jpg

832 ms

SLIM_255x84.jpg

SLIM_255x84.jpg

849 ms

mBillionth_255x84.jpg

mBillionth_255x84.jpg

830 ms

analytics.js

analytics.js

148 ms

2b90a6a8-873f-4b67-a22d-d818f3521094.js

2b90a6a8-873f-4b67-a22d-d818f3521094.js

962 ms

bg-comment.png

bg-comment.png

907 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

465 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

473 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

463 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

467 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

462 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

481 ms

ieVi2ZhZI2eCN5jzbjEETS9weq8-32meKCM.ttf

ieVi2ZhZI2eCN5jzbjEETS9weq8-32meKCM.ttf

484 ms

ieVl2ZhZI2eCN5jzbjEETS9weq8-59U.ttf

ieVl2ZhZI2eCN5jzbjEETS9weq8-59U.ttf

486 ms

ieVi2ZhZI2eCN5jzbjEETS9weq8-33mZKCM.ttf

ieVi2ZhZI2eCN5jzbjEETS9weq8-33mZKCM.ttf

482 ms

socicon.ttf

socicon.ttf

654 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

800 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

800 ms

collect

collect

398 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

444 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

446 ms

revolution.extension.navigation.min.js

revolution.extension.navigation.min.js

450 ms

revolution.extension.parallax.min.js

revolution.extension.parallax.min.js

586 ms

PlI9FlK4Jrl5Y9zNSyCi8A.ttf

PlI9FlK4Jrl5Y9zNSyCi8A.ttf

134 ms

Accessibility Review

zmessenger.com accessibility score

68

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

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

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

zmessenger.com SEO score

97

Search Engine Optimization Advices

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

zmessenger.com

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