Tools & Wizards About Us
phonenumberworld.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

phonenumberworld.com

Buy Vanity Phone Numbers, Toll Free and Local Numbers | Phone Number World

Page Load Speed

4 sec in total

First Response

218 ms

Resources Loaded

2 sec

Page Rendered

1.7 sec

phonenumberworld.com screenshot

About Website

Welcome to phonenumberworld.com homepage info - get ready to check Phone Number World best content right away, or after learning these important things about phonenumberworld.com

Buy a memorable vanity phone number for your business. Millions of local vanity phone numbers and toll-free phone numbers are available for you to increase business calls and boost sales.

Visit phonenumberworld.com

Key Findings

We analyzed Phonenumberworld.com page load time and found that the first response time was 218 ms and then it took 3.8 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

phonenumberworld.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value280 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

phonenumberworld.com

218 ms

out_pay.js

27 ms

chunk-vendors.2e368c5e.css

248 ms

app.f3db0039.css

128 ms

analytics.js

33 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 70% of them (44 requests) were addressed to the original Phonenumberworld.com, 8% (5 requests) were made to T1.mylivechat.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (707 ms) belongs to the original domain Phonenumberworld.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (35%)

Content Size

3.6 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phonenumberworld.com main page is 3.6 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 115.8 kB

  • Original 152.2 kB
  • After minification 151.1 kB
  • After compression 36.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 115.8 kB or 76% of the original size.

Image Optimization

-11%

Potential reduce by 235.3 kB

  • Original 2.1 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. Obviously, Phone Number World needs image optimization as it can save up to 235.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 891.8 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 426.5 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 891.8 kB or 68% of the original size.

CSS Optimization

-20%

Potential reduce by 10.2 kB

  • Original 50.0 kB
  • After minification 50.0 kB
  • After compression 39.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. Phonenumberworld.com needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 20% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phone Number World. 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

phonenumberworld.com

phonenumberworld.com

218 ms

out_pay.js

out_pay.js

27 ms

chunk-vendors.2e368c5e.css

chunk-vendors.2e368c5e.css

248 ms

app.f3db0039.css

app.f3db0039.css

128 ms

analytics.js

analytics.js

33 ms

chunk-882cffe8.7ea89531.css

chunk-882cffe8.7ea89531.css

125 ms

chunk-882cffe8.6b3473b8.js

chunk-882cffe8.6b3473b8.js

181 ms

chunk-79224dd4.90ab9a3f.js

chunk-79224dd4.90ab9a3f.js

125 ms

chunk-734adc76.d54048e5.css

chunk-734adc76.d54048e5.css

175 ms

chunk-734adc76.b30690cb.js

chunk-734adc76.b30690cb.js

303 ms

pcHome.c9d06a2c.css

pcHome.c9d06a2c.css

265 ms

pcHome.da7fe9b9.js

pcHome.da7fe9b9.js

367 ms

chunk-882cffe8.7ea89531.css

chunk-882cffe8.7ea89531.css

205 ms

chunk-882cffe8.6b3473b8.js

chunk-882cffe8.6b3473b8.js

329 ms

chunk-vendors.6a7d7614.js

chunk-vendors.6a7d7614.js

707 ms

app.b399cde2.js

app.b399cde2.js

368 ms

chunk-79224dd4.90ab9a3f.js

chunk-79224dd4.90ab9a3f.js

63 ms

chunk-734adc76.d54048e5.css

chunk-734adc76.d54048e5.css

64 ms

chunk-734adc76.b30690cb.js

chunk-734adc76.b30690cb.js

119 ms

pcHome.c9d06a2c.css

pcHome.c9d06a2c.css

123 ms

pcHome.da7fe9b9.js

pcHome.da7fe9b9.js

119 ms

header_bg.ec58dcca.png

header_bg.ec58dcca.png

585 ms

website_logo.7430ed28.png

website_logo.7430ed28.png

540 ms

at&t.c481651c.png

at&t.c481651c.png

541 ms

sprint.a5e9b913.png

sprint.a5e9b913.png

540 ms

t_mobile.eb6cdee4.png

t_mobile.eb6cdee4.png

540 ms

verizon.fbab59c7.png

verizon.fbab59c7.png

543 ms

x_finity.e907be54.png

x_finity.e907be54.png

542 ms

vonage.58b91ab7.png

vonage.58b91ab7.png

541 ms

frontier.35332735.png

frontier.35332735.png

541 ms

computer.9569ae04.png

computer.9569ae04.png

585 ms

header1.b102d3e4.png

header1.b102d3e4.png

543 ms

header2.b0d5bac4.png

header2.b0d5bac4.png

544 ms

header3.0e4654ad.png

header3.0e4654ad.png

582 ms

header4.85b7e316.png

header4.85b7e316.png

581 ms

header5.71822e5d.png

header5.71822e5d.png

581 ms

instagram.805a0cb2.png

instagram.805a0cb2.png

581 ms

media_4.2ea898c9.png

media_4.2ea898c9.png

613 ms

mastercard.83d83bc3.png

mastercard.83d83bc3.png

611 ms

visa.8938fa22.png

visa.8938fa22.png

613 ms

american_express.9b7d6412.png

american_express.9b7d6412.png

613 ms

chatinline.aspx

chatinline.aspx

538 ms

element-icons.535877f5.woff

element-icons.535877f5.woff

512 ms

queryRecommendNumbers

queryRecommendNumbers

379 ms

patternList

patternList

181 ms

stateList

stateList

233 ms

getAreaCode

getAreaCode

129 ms

collect

collect

23 ms

livechat2.aspx

livechat2.aspx

332 ms

chunk-057f8663.15c249ab.css

chunk-057f8663.15c249ab.css

90 ms

element-icons.732389de.ttf

element-icons.732389de.ttf

293 ms

css

css

33 ms

chatinline.css

chatinline.css

32 ms

resources2.aspx

resources2.aspx

137 ms

chunk-067d9184.7dbdbd19.css

chunk-067d9184.7dbdbd19.css

125 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

22 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

31 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

64 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

66 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

66 ms

chunk-33101eaa.e1859c60.css

chunk-33101eaa.e1859c60.css

73 ms

livechatinit2.js

livechatinit2.js

33 ms

InlineChatRoundOffline_18.png

InlineChatRoundOffline_18.png

32 ms

Accessibility Review

phonenumberworld.com accessibility score

74

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.

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

Form elements do not have associated labels

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

phonenumberworld.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

phonenumberworld.com 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

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

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

phonenumberworld.com

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