Tools & Wizards About Us
phoneslookup.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

phoneslookup.com

Reverse phone number lookup in USA. Check the number before picking up! | PhonesLookup.com

Page Load Speed

4.7 sec in total

First Response

172 ms

Resources Loaded

635 ms

Page Rendered

3.9 sec

phoneslookup.com screenshot

About Website

Welcome to phoneslookup.com homepage info - get ready to check Phones Lookup best content right away, or after learning these important things about phoneslookup.com

Find out who is calling you using our website. Find out if it's spam, a robot call or a marketing survey. Be safe thanks to PhonesLookup.

Visit phoneslookup.com

Key Findings

We analyzed Phoneslookup.com page load time and found that the first response time was 172 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

phoneslookup.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value3,550 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.595

11/100

15%

TTI (Time to Interactive)

Value15.0 s

8/100

10%

Network Requests Diagram

phoneslookup.com

172 ms

gtm.js

106 ms

adsbygoogle.js

153 ms

app.js

148 ms

favicon-96x96.png

32 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 58% of them (7 requests) were addressed to the original Phoneslookup.com, 17% (2 requests) were made to Googletagmanager.com and 17% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (227 ms) relates to the external source Pagead2.googlesyndication.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.4 kB (11%)

Content Size

735.9 kB

After Optimization

658.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Phoneslookup.com main page is 735.9 kB. 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. Javascripts take 433.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 76.5 kB

  • Original 94.1 kB
  • After minification 94.1 kB
  • After compression 17.7 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 76.5 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 953 B

  • Original 208.1 kB
  • After minification 207.1 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. Phones Lookup images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 27 B

  • Original 433.7 kB
  • After minification 433.7 kB
  • After compression 433.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.

Requests Breakdown

Number of requests can be reduced by 5 (45%)

Requests Now

11

After Optimization

6

  • AJAX
  • Images
  • JavaScript

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

phoneslookup.com

phoneslookup.com

172 ms

gtm.js

gtm.js

106 ms

adsbygoogle.js

adsbygoogle.js

153 ms

app.js

app.js

148 ms

favicon-96x96.png

favicon-96x96.png

32 ms

phone_sick.jpg

phone_sick.jpg

194 ms

bv-wide-bg.jpg

bv-wide-bg.jpg

106 ms

bv-square-bg.jpg

bv-square-bg.jpg

21 ms

main.js

main.js

9 ms

js

js

85 ms

show_ads_impl.js

show_ads_impl.js

227 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

76 ms

Accessibility Review

phoneslookup.com accessibility score

68

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

[role]s are not contained by their required parent element

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

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

Some elements have a [tabindex] value greater than 0

Best Practices

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

phoneslookup.com SEO score

100

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

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

phoneslookup.com

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