Tools & Wizards About Us
fones.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

fones.com

Mobile Phones & Accessories Wholesale | Sim Cards Suppliers UK - Elite Mobile

Page Load Speed

3.6 sec in total

First Response

186 ms

Resources Loaded

2.8 sec

Page Rendered

621 ms

fones.com screenshot

About Website

Visit fones.com now to see the best up-to-date Fones content and also check out these interesting facts you probably never knew about fones.com

Elite Mobile: Elite Mobile is UK's No.1 sim card distributor. Buy mobile phones, accessories & sim cards in wholesale at best prices.

Visit fones.com

Key Findings

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

Performance Metrics

fones.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

fones.com

186 ms

elitemobile.com

211 ms

www.elitemobile.com

215 ms

www.elitemobile.com

428 ms

css

42 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fones.com, 75% (40 requests) were made to Elitemobile.com and 9% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Elitemobile.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.3 kB (29%)

Content Size

196.6 kB

After Optimization

140.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Fones.com main page is 196.6 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. 40% of websites need less resources to load. Javascripts take 126.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 20.5 kB

  • Original 25.9 kB
  • After minification 20.1 kB
  • After compression 5.3 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 5.8 kB, which is 22% 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 20.5 kB or 79% of the original size.

JavaScript Optimization

-25%

Potential reduce by 32.0 kB

  • Original 126.7 kB
  • After minification 126.7 kB
  • After compression 94.7 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 32.0 kB or 25% of the original size.

CSS Optimization

-9%

Potential reduce by 3.8 kB

  • Original 44.1 kB
  • After minification 44.1 kB
  • After compression 40.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. Fones.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

20

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fones.com

fones.com

186 ms

elitemobile.com

elitemobile.com

211 ms

www.elitemobile.com

www.elitemobile.com

215 ms

www.elitemobile.com

www.elitemobile.com

428 ms

css

css

42 ms

flexslider.css

flexslider.css

92 ms

bootstrap.min.css

bootstrap.min.css

276 ms

font-awesome.min.css

font-awesome.min.css

273 ms

style.css

style.css

267 ms

sweetalert.css

sweetalert.css

235 ms

jquery.min.js

jquery.min.js

457 ms

jquery.validate.js

jquery.validate.js

275 ms

js

js

68 ms

script.js

script.js

311 ms

jquery.inview.js

jquery.inview.js

344 ms

bootstrap.min.js

bootstrap.min.js

361 ms

jquery.flexslider.js

jquery.flexslider.js

373 ms

flexslider-custom.js

flexslider-custom.js

370 ms

sweetalert.min.js

sweetalert.min.js

394 ms

numscroller-1.0.js

numscroller-1.0.js

427 ms

bootstrap-extras-margins-padding.css

bootstrap-extras-margins-padding.css

180 ms

analytics.js

analytics.js

68 ms

up-arrow.svg

up-arrow.svg

94 ms

search_icon.png

search_icon.png

106 ms

logo.png

logo.png

104 ms

search-icon.png

search-icon.png

103 ms

new-logo.png

new-logo.png

92 ms

banner-1.jpg

banner-1.jpg

252 ms

web_icons-01-new1.svg

web_icons-01-new1.svg

238 ms

web_icons-02.svg

web_icons-02.svg

245 ms

web_icons-03.svg

web_icons-03.svg

242 ms

web_icons-04.svg

web_icons-04.svg

239 ms

web_icons-06.svg

web_icons-06.svg

247 ms

contact_us-05.svg

contact_us-05.svg

282 ms

EE.png

EE.png

429 ms

O2.png

O2.png

365 ms

three.png

three.png

724 ms

vodafone.png

vodafone.png

376 ms

giffgaff.png

giffgaff.png

395 ms

lebara.png

lebara.png

590 ms

VOXI_small.png

VOXI_small.png

458 ms

SMARTY_LOGO.png

SMARTY_LOGO.png

475 ms

footer_award_banner_on_retailer24.png

footer_award_banner_on_retailer24.png

552 ms

count-bg.png

count-bg.png

1257 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

39 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

39 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

48 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

48 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

49 ms

widget

widget

572 ms

collect

collect

24 ms

collect

collect

30 ms

js

js

60 ms

Accessibility Review

fones.com accessibility score

48

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

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

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

fones.com best practices score

50

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fones.com SEO score

76

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fones.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 Fones.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

fones.com

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