Tools & Wizards About Us
numbber.net screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

numbber.net

Avec Numbber, conservez votre numéro perso, perso !

Page Load Speed

2 sec in total

First Response

233 ms

Resources Loaded

1.5 sec

Page Rendered

303 ms

numbber.net screenshot

About Website

Welcome to numbber.net homepage info - get ready to check Numbber best content right away, or after learning these important things about numbber.net

Une application pour votre smartphone fournissant un numéro de téléphone alternatif, qui sonne sur votre portable, en fonction de votre disponibilité.

Visit numbber.net

Key Findings

We analyzed Numbber.net page load time and found that the first response time was 233 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

numbber.net performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

numbber.net

233 ms

www.numbber.net

234 ms

style.css

190 ms

font-awesome.css

8 ms

css

24 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 73% of them (22 requests) were addressed to the original Numbber.net, 10% (3 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (767 ms) belongs to the original domain Numbber.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 329.6 kB (31%)

Content Size

1.1 MB

After Optimization

729.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Numbber.net 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. 30% of websites need less resources to load. Images take 692.1 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 9.1 kB

  • Original 12.7 kB
  • After minification 11.2 kB
  • After compression 3.5 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. This page needs HTML code to be minified as it can gain 1.5 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 9.1 kB or 72% of the original size.

Image Optimization

-9%

Potential reduce by 61.8 kB

  • Original 692.1 kB
  • After minification 630.2 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. Numbber images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 103.6 kB

  • Original 174.8 kB
  • After minification 173.3 kB
  • After compression 71.2 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 103.6 kB or 59% of the original size.

CSS Optimization

-86%

Potential reduce by 155.0 kB

  • Original 179.9 kB
  • After minification 142.5 kB
  • After compression 24.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. Numbber.net needs all CSS files to be minified and compressed as it can save up to 155.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (29%)

Requests Now

24

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

numbber.net

numbber.net

233 ms

www.numbber.net

www.numbber.net

234 ms

style.css

style.css

190 ms

font-awesome.css

font-awesome.css

8 ms

css

css

24 ms

jquery.js

jquery.js

275 ms

bootstrap.min.js

bootstrap.min.js

171 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

181 ms

jquery.sequence.min.js

jquery.sequence.min.js

229 ms

jquery.pageslide.min.js

jquery.pageslide.min.js

229 ms

main-bg.min.js

main-bg.min.js

273 ms

contact.js

contact.js

288 ms

analytics.js

analytics.js

18 ms

apple_2.png

apple_2.png

99 ms

google.png

google.png

99 ms

slide01_img.png

slide01_img.png

469 ms

slide02_img.png

slide02_img.png

438 ms

smiley1.png

smiley1.png

114 ms

smiley2.png

smiley2.png

136 ms

tem1.png

tem1.png

362 ms

tem2.png

tem2.png

368 ms

tem3.png

tem3.png

280 ms

iphone-tilt_img.png

iphone-tilt_img.png

767 ms

bg-newsletter.jpg

bg-newsletter.jpg

362 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

45 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

45 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

45 ms

collect

collect

51 ms

bg-image.jpg

bg-image.jpg

458 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

9 ms

Accessibility Review

numbber.net accessibility score

75

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

numbber.net best practices score

83

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

SEO Factors

numbber.net SEO score

80

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Numbber.net can be misinterpreted by Google and other search engines. Our service has detected that French 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 Numbber.net 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

numbber.net

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