Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

numly.io

Home | Numly™, Inc. - Better Leaders. Resilient Teams.

Page Load Speed

2 sec in total

First Response

7 ms

Resources Loaded

1.3 sec

Page Rendered

720 ms

numly.io screenshot

About Website

Click here to check amazing Numly content. Otherwise, check out these important facts you probably never knew about numly.io

Numly™, Inc. Official Site | The Art and Science of Cultivating Soft Skills to Drive Employee Engagement & Accelerate Professional and Business Growth.

Visit numly.io

Key Findings

We analyzed Numly.io page load time and found that the first response time was 7 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

numly.io performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value20.8 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value1,800 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value1.868

0/100

15%

TTI (Time to Interactive)

Value22.7 s

1/100

10%

Network Requests Diagram

numly.io

7 ms

numly.io

401 ms

gtm.js

70 ms

style.min.css

9 ms

image-map-pro.min.css

16 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 81% of them (99 requests) were addressed to the original Numly.io, 6% (7 requests) were made to Use.typekit.net and 3% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (723 ms) relates to the external source Seal.godaddy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (40%)

Content Size

2.7 MB

After Optimization

1.6 MB

In fact, the total size of Numly.io main page is 2.7 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. 85% 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 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 127.3 kB

  • Original 162.7 kB
  • After minification 149.6 kB
  • After compression 35.4 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 127.3 kB or 78% of the original size.

Image Optimization

-39%

Potential reduce by 975.2 kB

  • Original 2.5 MB
  • After minification 1.6 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. Obviously, Numly needs image optimization as it can save up to 975.2 kB or 39% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 625 B

  • Original 23.2 kB
  • After minification 23.2 kB
  • After compression 22.6 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

-2%

Potential reduce by 217 B

  • Original 10.9 kB
  • After minification 10.8 kB
  • After compression 10.7 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. Numly.io has all CSS files already compressed.

Requests Breakdown

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

Requests Now

112

After Optimization

77

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

Accessibility Review

numly.io accessibility score

86

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-hidden="true"] elements contain focusable descendents

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

numly.io 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

numly.io SEO score

86

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

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 Numly.io 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 Numly.io 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 data is detected on the main page of Numly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: