Tools & Wizards About Us
metric.works screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

metric.works

Home - MetricWorks | Future-Proof Mobile Measurement

Page Load Speed

4.2 sec in total

First Response

229 ms

Resources Loaded

3.2 sec

Page Rendered

778 ms

metric.works screenshot

About Website

Welcome to metric.works homepage info - get ready to check Metric best content right away, or after learning these important things about metric.works

Turn key incrementality measurement. Fully automated MMM crafted by mobile experts. Built for a privacy-centric world.

Visit metric.works

Key Findings

We analyzed Metric.works page load time and found that the first response time was 229 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

metric.works performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value4,370 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

metric.works

229 ms

metric.works

41 ms

www.metric.works

93 ms

www.metricworks.ai

1928 ms

metricworks-v2.webflow.9965b09f5.css

127 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Metric.works, 81% (44 requests) were made to Cdn.prod.website-files.com and 9% (5 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Metricworks.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.0 kB (7%)

Content Size

2.1 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Metric.works main page is 2.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. 55% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 68.3 kB

  • Original 91.3 kB
  • After minification 91.1 kB
  • After compression 23.0 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 68.3 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 90.1 kB

  • Original 1.9 MB
  • After minification 1.8 MB

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. Metric images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 205 B

  • Original 179.5 kB
  • After minification 179.5 kB
  • After compression 179.3 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

-6%

Potential reduce by 1.4 kB

  • Original 22.8 kB
  • After minification 22.8 kB
  • After compression 21.4 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. Metric.works has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (31%)

Requests Now

49

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

metric.works

metric.works

229 ms

metric.works

metric.works

41 ms

www.metric.works

www.metric.works

93 ms

www.metricworks.ai

www.metricworks.ai

1928 ms

metricworks-v2.webflow.9965b09f5.css

metricworks-v2.webflow.9965b09f5.css

127 ms

fs-cc.js

fs-cc.js

15 ms

swiper-bundle.min.css

swiper-bundle.min.css

21 ms

swiper-bundle.min.js

swiper-bundle.min.js

23 ms

jquery-3.5.1.min.dc5e7f18c8.js

jquery-3.5.1.min.dc5e7f18c8.js

16 ms

webflow.004b74ed3.js

webflow.004b74ed3.js

170 ms

gsap.min.js

gsap.min.js

21 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

21 ms

66f2dc78be20e9ff614c5e81_mw%20logo.svg

66f2dc78be20e9ff614c5e81_mw%20logo.svg

63 ms

66f42e08e96d932879271968_metricworks%20logo%20dark.svg

66f42e08e96d932879271968_metricworks%20logo%20dark.svg

151 ms

66f6b91a9e284b1a76d46911_Content.svg

66f6b91a9e284b1a76d46911_Content.svg

164 ms

66f6b962158c1b8d8f74731b_open%20icon.svg

66f6b962158c1b8d8f74731b_open%20icon.svg

129 ms

66f6b9715c728a6c6c4243ef_close%20icon.svg

66f6b9715c728a6c6c4243ef_close%20icon.svg

153 ms

66f2982ed1b2dcd094ea554c_mw-arrow.svg

66f2982ed1b2dcd094ea554c_mw-arrow.svg

118 ms

66f29c54e8928b1cedbd6f83_funplus.avif

66f29c54e8928b1cedbd6f83_funplus.avif

129 ms

66f29c55e8928b1cedbd6fe5_kabam.avif

66f29c55e8928b1cedbd6fe5_kabam.avif

205 ms

66f29c55e8928b1cedbd704d_blizzard.avif

66f29c55e8928b1cedbd704d_blizzard.avif

211 ms

66f30d49c297d87c81e93dbc_new-google-favicon-512%207.svg

66f30d49c297d87c81e93dbc_new-google-favicon-512%207.svg

235 ms

66f30d5711d2ff7af28fd41f_new-google-favicon-512%206.svg

66f30d5711d2ff7af28fd41f_new-google-favicon-512%206.svg

206 ms

66f30d6b11d2ff7af28ffa19_new-google-favicon-512%201.svg

66f30d6b11d2ff7af28ffa19_new-google-favicon-512%201.svg

249 ms

66f30d8b96333f345543a7df_Kabam_Logo.svg

66f30d8b96333f345543a7df_Kabam_Logo.svg

220 ms

66f30d94b5f801502e90efce_FunPlus_main-Logo_Vertical_Orange_RGB.svg

66f30d94b5f801502e90efce_FunPlus_main-Logo_Vertical_Orange_RGB.svg

290 ms

66f30d9afbbe8bc0efa0f515_images.svg

66f30d9afbbe8bc0efa0f515_images.svg

271 ms

66f6934dba57f15c086734ee_jamcity.avif

66f6934dba57f15c086734ee_jamcity.avif

321 ms

66f69367d61b7dc35420276e_mythical.avif

66f69367d61b7dc35420276e_mythical.avif

293 ms

67194c0557f5899aa9f2784e_blizzard%20logo.png

67194c0557f5899aa9f2784e_blizzard%20logo.png

288 ms

66f6938add438242ec673219_nexon-logo.avif

66f6938add438242ec673219_nexon-logo.avif

298 ms

66f3da49fb3af09052a13721_mw-arrow-dark.svg

66f3da49fb3af09052a13721_mw-arrow-dark.svg

377 ms

66f2a54dc553ca1d78714907_mw-pie.svg

66f2a54dc553ca1d78714907_mw-pie.svg

376 ms

66f2ae7a6d39ee8fc1b5939f_mw-network.svg

66f2ae7a6d39ee8fc1b5939f_mw-network.svg

360 ms

66f2abdb293046d76969ce60_mw-realtime.svg

66f2abdb293046d76969ce60_mw-realtime.svg

418 ms

66f6ad7dbdeb795e9bd2ccc2_mw-map.avif

66f6ad7dbdeb795e9bd2ccc2_mw-map.avif

380 ms

670b3451500617486d050376_icon.svg

670b3451500617486d050376_icon.svg

400 ms

670b343bd43d7adda22cec67_icon.svg

670b343bd43d7adda22cec67_icon.svg

423 ms

670b3446d6ccc28dda60062d_icon.svg

670b3446d6ccc28dda60062d_icon.svg

439 ms

670b339ee0143bf29fb1dfc8_Vector.svg

670b339ee0143bf29fb1dfc8_Vector.svg

433 ms

670b80f54cd3dac43837b737_Table%201.png

670b80f54cd3dac43837b737_Table%201.png

543 ms

66f3d54a1223d151bd53030a_kabam.png

66f3d54a1223d151bd53030a_kabam.png

514 ms

66f3d3f9e93be1c1f498f1bc_0d2bead9abc6fbe7397a1532ad726440.avif

66f3d3f9e93be1c1f498f1bc_0d2bead9abc6fbe7397a1532ad726440.avif

477 ms

670405bbd54e46b3f3dcfd88_logo-mobilityware-1.png

670405bbd54e46b3f3dcfd88_logo-mobilityware-1.png

584 ms

66f426a562492921c0e00463_chirs%20image.avif

66f426a562492921c0e00463_chirs%20image.avif

482 ms

66f426fb18be69f08e5cb224_zehong%20iamge.avif

66f426fb18be69f08e5cb224_zehong%20iamge.avif

531 ms

66f7dc6c418ca91d088c80d8_GSW-Touchpoints%20(1).avif

66f7dc6c418ca91d088c80d8_GSW-Touchpoints%20(1).avif

530 ms

placeholder.60f9b1840c.svg

placeholder.60f9b1840c.svg

462 ms

66faf161d060964b8c3ca28c_66f7da1864b489d660679445_Methods-of-Measurement-Diagram.png

66faf161d060964b8c3ca28c_66f7da1864b489d660679445_Methods-of-Measurement-Diagram.png

604 ms

66faf161d060964b8c3ca289_66f7dc9c3dbb3613d4a077b4_66f7dc6c418ca91d088c80d8_GSW-Touchpoints%252520(1).webp

66faf161d060964b8c3ca289_66f7dc9c3dbb3613d4a077b4_66f7dc6c418ca91d088c80d8_GSW-Touchpoints%252520(1).webp

483 ms

66f7d96a03d11986ab5c73e4_Unicorn-MetricWorks-May-1st-2024-400x250.avif

66f7d96a03d11986ab5c73e4_Unicorn-MetricWorks-May-1st-2024-400x250.avif

474 ms

66ff94b1623a37bd7327becf_66f7d98d0855a2b7db1691ce_Unicorn-MetricWorks-May-1st-2024-e1714582518358.png

66ff94b1623a37bd7327becf_66f7d98d0855a2b7db1691ce_Unicorn-MetricWorks-May-1st-2024-e1714582518358.png

505 ms

66f7d8b4da29663d71ae86c7_GameWorks-Header-2-400x250.avif

66f7d8b4da29663d71ae86c7_GameWorks-Header-2-400x250.avif

449 ms

66ff94c6da5fa65f1445b031_66f7d8d7f4ec403186bf769c_GameWorks-Header-1.png

66ff94c6da5fa65f1445b031_66f7d8d7f4ec403186bf769c_GameWorks-Header-1.png

624 ms

Accessibility Review

metric.works accessibility score

98

Accessibility Issues

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

metric.works 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

Missing source maps for large first-party JavaScript

SEO Factors

metric.works SEO score

92

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

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

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 Metric.works 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 Metric.works 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

metric.works

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