Tools & Wizards About Us
fonesat.ie screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fonesat.ie

Account Suspended

Page Load Speed

7.4 sec in total

First Response

2.7 sec

Resources Loaded

4.5 sec

Page Rendered

194 ms

fonesat.ie screenshot

About Website

Welcome to fonesat.ie homepage info - get ready to check Fonesat best content right away, or after learning these important things about fonesat.ie

FoneSat has been the longest operating mobile phone repair shop in Cork, trading since 1994. We specialise in mobile phone repairs and unlocking.

Visit fonesat.ie

Key Findings

We analyzed Fonesat.ie page load time and found that the first response time was 2.7 sec and then it took 4.7 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

fonesat.ie performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.623

10/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

fonesat.ie

2745 ms

style.css

271 ms

dashicons.min.css

270 ms

thickbox.css

191 ms

css

22 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 87% of them (67 requests) were addressed to the original Fonesat.ie, 8% (6 requests) were made to Fonts.googleapis.com and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Fonesat.ie.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.0 kB (9%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fonesat.ie main page is 1.3 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. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 24.6 kB

  • Original 32.3 kB
  • After minification 29.0 kB
  • After compression 7.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 24.6 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 44.4 kB

  • Original 1.1 MB
  • After minification 1.0 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. Fonesat images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 24.9 kB

  • Original 88.1 kB
  • After minification 88.1 kB
  • After compression 63.2 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 24.9 kB or 28% of the original size.

CSS Optimization

-20%

Potential reduce by 15.2 kB

  • Original 75.7 kB
  • After minification 75.7 kB
  • After compression 60.5 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. Fonesat.ie needs all CSS files to be minified and compressed as it can save up to 15.2 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (61%)

Requests Now

72

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fonesat.ie

fonesat.ie

2745 ms

style.css

style.css

271 ms

dashicons.min.css

dashicons.min.css

270 ms

thickbox.css

thickbox.css

191 ms

css

css

22 ms

css

css

35 ms

css

css

67 ms

css

css

67 ms

css

css

42 ms

css

css

66 ms

prettyPhoto.css

prettyPhoto.css

188 ms

tipsy.css

tipsy.css

190 ms

flexslider.css

flexslider.css

260 ms

slider-nivo.css

slider-nivo.css

316 ms

extra.min.css

extra.min.css

317 ms

style.min.css

style.min.css

357 ms

styles.css

styles.css

359 ms

menu-image.css

menu-image.css

360 ms

wpmi.css

wpmi.css

360 ms

layerslider.css

layerslider.css

364 ms

jquery.js

jquery.js

541 ms

jquery-migrate.min.js

jquery-migrate.min.js

440 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

439 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

438 ms

jquery.tipsy.js

jquery.tipsy.js

442 ms

jquery.tweetable.js

jquery.tweetable.js

458 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

525 ms

jquery.cycle.min.js

jquery.cycle.min.js

528 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

527 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

529 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

565 ms

jquery-easing-1.3.js

jquery-easing-1.3.js

616 ms

menu.css

menu.css

614 ms

client.css

client.css

615 ms

fsml-base.css

fsml-base.css

625 ms

thickbox.js

thickbox.js

550 ms

underscore.min.js

underscore.min.js

551 ms

shortcode.min.js

shortcode.min.js

576 ms

media-upload.min.js

media-upload.min.js

577 ms

jquery.custom.js

jquery.custom.js

590 ms

scripts.js

scripts.js

593 ms

contact.js

contact.js

568 ms

wp-embed.min.js

wp-embed.min.js

576 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

498 ms

new-logo1.png

new-logo1.png

436 ms

iphonexr_50x50.jpg

iphonexr_50x50.jpg

179 ms

ipad-50x50.jpg

ipad-50x50.jpg

180 ms

ipod-50x50.jpg

ipod-50x50.jpg

189 ms

s10plus_50x50.jpg

s10plus_50x50.jpg

219 ms

laptop_50x50.jpg

laptop_50x50.jpg

263 ms

PS4_50x50.jpg

PS4_50x50.jpg

269 ms

xboxone_50x50.jpg

xboxone_50x50.jpg

266 ms

resize-15814325001059939157ghd.jpg

resize-15814325001059939157ghd.jpg

277 ms

resize-1581685245198984372satellitedish.jpg

resize-1581685245198984372satellitedish.jpg

307 ms

slide0.png

slide0.png

619 ms

resize-1581346827176028144unlockingright.png

resize-1581346827176028144unlockingright.png

701 ms

laptoprepair1_608x269.jpg

laptoprepair1_608x269.jpg

449 ms

resize-1581083145288440025slide.png

resize-1581083145288440025slide.png

607 ms

resize-1581080881285638547slide5.jpg

resize-1581080881285638547slide5.jpg

404 ms

slide5.jpg

slide5.jpg

512 ms

brokenphone.jpg

brokenphone.jpg

530 ms

shop.png

shop.png

539 ms

checkbox.png

checkbox.png

602 ms

truck.png

truck.png

617 ms

wrench.png

wrench.png

629 ms

008.jpg

008.jpg

860 ms

boxed-container-shadow.png

boxed-container-shadow.png

690 ms

slider-separator.png

slider-separator.png

727 ms

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

8 ms

RrQfboBx-C5_XxrBaw.ttf

RrQfboBx-C5_XxrBaw.ttf

16 ms

qFdb35qfgYFjGy5hukqqhw5XeRgdi1ryd6DMGbo.ttf

qFdb35qfgYFjGy5hukqqhw5XeRgdi1ryd6DMGbo.ttf

18 ms

rax5HiePvdgXPmmMHcIPYShdu0o.ttf

rax5HiePvdgXPmmMHcIPYShdu0o.ttf

17 ms

loadingAnimation.gif

loadingAnimation.gif

568 ms

lessthen960.css

lessthen960.css

93 ms

lessthen600.css

lessthen600.css

103 ms

lessthen480.css

lessthen480.css

92 ms

slider-control.png

slider-control.png

91 ms

Accessibility Review

fonesat.ie 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.

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

fonesat.ie best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fonesat.ie SEO score

93

Search Engine Optimization Advices

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

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 Fonesat.ie 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 Fonesat.ie 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

fonesat.ie

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