Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fonebank.com

Sell my mobile phone recycling | Earn Cash upto £430 – Recycle online

Page Load Speed

11 sec in total

First Response

3.8 sec

Resources Loaded

7 sec

Page Rendered

168 ms

fonebank.com screenshot

About Website

Welcome to fonebank.com homepage info - get ready to check Fonebank best content for United Kingdom right away, or after learning these important things about fonebank.com

Get Cash for mobile phones from most reliable mobile phone recycling company. Selling Your Mobile Phones for Cash with Great Prices and Very Fast Payment

Visit fonebank.com

Key Findings

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

Performance Metrics

fonebank.com performance score

0

Network Requests Diagram

fonebank.com

3842 ms

www.fonebank.com

885 ms

jquery.min.js

65 ms

jquery-migrate-1.2.1.min.js

451 ms

main.css

536 ms

Our browser made a total of 152 requests to load all elements on the main page. We found that 53% of them (81 requests) were addressed to the original Fonebank.com, 7% (10 requests) were made to Static.xx.fbcdn.net and 6% (9 requests) were made to Widget.trustpilot.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Fonebank.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 977.1 kB (57%)

Content Size

1.7 MB

After Optimization

733.6 kB

In fact, the total size of Fonebank.com main page is 1.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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 118.1 kB

  • Original 139.7 kB
  • After minification 125.8 kB
  • After compression 21.6 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 118.1 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 23.9 kB

  • Original 410.4 kB
  • After minification 386.6 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. Fonebank images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 767.2 kB

  • Original 1.1 MB
  • After minification 856.8 kB
  • After compression 315.4 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 767.2 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 67.9 kB

  • Original 77.9 kB
  • After minification 52.8 kB
  • After compression 10.0 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. Fonebank.com needs all CSS files to be minified and compressed as it can save up to 67.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (46%)

Requests Now

147

After Optimization

79

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

SEO Factors

fonebank.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fonebank.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Fonebank.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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