Tools & Wizards About Us
webuyfaultyphones.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

webuyfaultyphones.com

Sell Your iPhone or iPad Online | WeBuyFaultyPhones | iPhone | iPad

Page Load Speed

5.1 sec in total

First Response

496 ms

Resources Loaded

4.5 sec

Page Rendered

191 ms

webuyfaultyphones.com screenshot

About Website

Visit webuyfaultyphones.com now to see the best up-to-date We Buy Faulty Phones content and also check out these interesting facts you probably never knew about webuyfaultyphones.com

Sell us your iPhone or iPad. Here at WeBuyFaultyPhones, we will take your old, faulty or unwanted iphone and iPad and pay you for it. It’s that simple.

Visit webuyfaultyphones.com

Key Findings

We analyzed Webuyfaultyphones.com page load time and found that the first response time was 496 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

webuyfaultyphones.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value680 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

webuyfaultyphones.com

496 ms

gtm.js

43 ms

6e0lv.css

174 ms

6dtlk.css

246 ms

e7czy.css

174 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 32% of them (27 requests) were addressed to the original Webuyfaultyphones.com, 56% (48 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (559 ms) belongs to the original domain Webuyfaultyphones.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.9 kB (43%)

Content Size

609.4 kB

After Optimization

344.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webuyfaultyphones.com main page is 609.4 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. 70% of websites need less resources to load. HTML takes 277.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 235.7 kB

  • Original 277.5 kB
  • After minification 272.7 kB
  • After compression 41.9 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 235.7 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 121.4 kB
  • After minification 121.4 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. We Buy Faulty Phones images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 20.6 kB

  • Original 163.6 kB
  • After minification 163.6 kB
  • After compression 142.9 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 20.6 kB or 13% of the original size.

CSS Optimization

-18%

Potential reduce by 8.6 kB

  • Original 46.9 kB
  • After minification 46.9 kB
  • After compression 38.3 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. Webuyfaultyphones.com needs all CSS files to be minified and compressed as it can save up to 8.6 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (71%)

Requests Now

35

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webuyfaultyphones.com

webuyfaultyphones.com

496 ms

gtm.js

gtm.js

43 ms

6e0lv.css

6e0lv.css

174 ms

6dtlk.css

6dtlk.css

246 ms

e7czy.css

e7czy.css

174 ms

ahis.js

ahis.js

179 ms

w.js

w.js

17 ms

6e0lw.js

6e0lw.js

259 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

18 ms

6e0lv.css

6e0lv.css

247 ms

js

js

55 ms

2kz8s.css

2kz8s.css

348 ms

jquery.min.js

jquery.min.js

384 ms

jquery-migrate.min.js

jquery-migrate.min.js

349 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

349 ms

add-to-cart.min.js

add-to-cart.min.js

349 ms

js.cookie.min.js

js.cookie.min.js

360 ms

woocommerce.min.js

woocommerce.min.js

383 ms

scripts.min.js

scripts.min.js

559 ms

jquery.fitvids.js

jquery.fitvids.js

423 ms

common.js

common.js

459 ms

wp_footer.js

wp_footer.js

460 ms

g.gif

g.gif

13 ms

wbfp-logo-master-web.svg

wbfp-logo-master-web.svg

202 ms

webuy-background.jpg

webuy-background.jpg

267 ms

select-your-phone.png

select-your-phone.png

220 ms

send-us-your-phone.png

send-us-your-phone.png

303 ms

get-paid.png

get-paid.png

318 ms

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

40 ms

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

50 ms

pxiEyp8kv8JHgFVrJJnedA.woff

pxiEyp8kv8JHgFVrJJnedA.woff

41 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

41 ms

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

41 ms

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

49 ms

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

57 ms

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

57 ms

pxiGyp8kv8JHgFVrLPTufntG.woff

pxiGyp8kv8JHgFVrLPTufntG.woff

56 ms

pxiGyp8kv8JHgFVrLPTufntF.ttf

pxiGyp8kv8JHgFVrLPTufntF.ttf

57 ms

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

56 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

57 ms

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

68 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

68 ms

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

68 ms

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

64 ms

font

font

67 ms

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

67 ms

AMOTz46Cs2uTAOCudlkpnccX.woff

AMOTz46Cs2uTAOCudlkpnccX.woff

110 ms

AMOTz46Cs2uTAOCudlkpnccU.ttf

AMOTz46Cs2uTAOCudlkpnccU.ttf

70 ms

AMOQz46Cs2uTAOCmhXo6.woff

AMOQz46Cs2uTAOCmhXo6.woff

188 ms

AMOQz46Cs2uTAOCmhXo5.ttf

AMOQz46Cs2uTAOCmhXo5.ttf

68 ms

AMOTz46Cs2uTAOCuLlgpnccX.woff

AMOTz46Cs2uTAOCuLlgpnccX.woff

178 ms

AMOTz46Cs2uTAOCuLlgpnccU.ttf

AMOTz46Cs2uTAOCuLlgpnccU.ttf

67 ms

AMOTz46Cs2uTAOCuPl8pnccX.woff

AMOTz46Cs2uTAOCuPl8pnccX.woff

160 ms

AMOTz46Cs2uTAOCuPl8pnccU.ttf

AMOTz46Cs2uTAOCuPl8pnccU.ttf

102 ms

AMOTz46Cs2uTAOCuIlwpnccX.woff

AMOTz46Cs2uTAOCuIlwpnccX.woff

122 ms

AMOTz46Cs2uTAOCuIlwpnccU.ttf

AMOTz46Cs2uTAOCuIlwpnccU.ttf

102 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4rQwOwpmPQ.woff

4UaZrEtFpBI4f1ZSIK9d4LjJ4rQwOwpmPQ.woff

103 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4rQwOwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4rQwOwpmPg.ttf

104 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4tMwOwpmPQ.woff

4UaZrEtFpBI4f1ZSIK9d4LjJ4tMwOwpmPQ.woff

104 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4tMwOwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4tMwOwpmPg.ttf

104 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4vowOwpmPQ.woff

4UaZrEtFpBI4f1ZSIK9d4LjJ4vowOwpmPQ.woff

105 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4vowOwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4vowOwpmPg.ttf

106 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4o0wOwpmPQ.woff

4UaZrEtFpBI4f1ZSIK9d4LjJ4o0wOwpmPQ.woff

107 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4o0wOwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4o0wOwpmPg.ttf

107 ms

modules.woff

modules.woff

450 ms

xfbml.customerchat.js

xfbml.customerchat.js

61 ms

et-divi-dynamic-11-late.css

et-divi-dynamic-11-late.css

228 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4mE3OwpmPQ.woff

4UaZrEtFpBI4f1ZSIK9d4LjJ4mE3OwpmPQ.woff

76 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4mE3OwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4mE3OwpmPg.ttf

77 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM3OwpmPQ.woff

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM3OwpmPQ.woff

76 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM3OwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM3OwpmPg.ttf

70 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4g03OwpmPQ.woff

4UaZrEtFpBI4f1ZSIK9d4LjJ4g03OwpmPQ.woff

76 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4g03OwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4g03OwpmPg.ttf

72 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4tM3OwpmPQ.woff

4UaZrEtFpBI4f1ZSIK9d4LjJ4tM3OwpmPQ.woff

69 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4tM3OwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4tM3OwpmPg.ttf

70 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM2OwpmPQ.woff

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM2OwpmPQ.woff

73 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM2OwpmPg.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM2OwpmPg.ttf

71 ms

k3kUo8kEI-tA1RRcTZGmTlHGCaE.woff

k3kUo8kEI-tA1RRcTZGmTlHGCaE.woff

70 ms

k3kUo8kEI-tA1RRcTZGmTlHGCaI.ttf

k3kUo8kEI-tA1RRcTZGmTlHGCaI.ttf

68 ms

WidgetScript

WidgetScript

184 ms

js

js

183 ms

145 ms

154 ms

6dtlk.css

6dtlk.css

106 ms

6dtlk.css

6dtlk.css

92 ms

Accessibility Review

webuyfaultyphones.com accessibility score

77

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

webuyfaultyphones.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 Webuyfaultyphones.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 Webuyfaultyphones.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

webuyfaultyphones.com

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