Tools & Wizards About Us
fonesquare.pk screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

fonesquare.pk

Default Web Site Page

Page Load Speed

11 sec in total

First Response

1.6 sec

Resources Loaded

9.1 sec

Page Rendered

287 ms

fonesquare.pk screenshot

About Website

Visit fonesquare.pk now to see the best up-to-date Fonesquare content for Pakistan and also check out these interesting facts you probably never knew about fonesquare.pk

Buy laptops projectors and mobiles online in Pakistan. We ship to Lahore Karachi Islamabad & All Over Pakistan.

Visit fonesquare.pk

Key Findings

We analyzed Fonesquare.pk page load time and found that the first response time was 1.6 sec and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

fonesquare.pk performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.6 s

0/100

25%

SI (Speed Index)

Value24.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.166

71/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

www.fonesquare.pk

1600 ms

wp-emoji-release.min.js

579 ms

linearicons.min.css

755 ms

style.min.css

763 ms

jquery.selectBox.css

767 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 83% of them (84 requests) were addressed to the original Fonesquare.pk, 5% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Fonesquare.pk.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fonesquare.pk main page is 1.2 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. 65% of websites need less resources to load. Javascripts take 445.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 103.9 kB

  • Original 133.2 kB
  • After minification 129.3 kB
  • After compression 29.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. 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 103.9 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 13.6 kB

  • Original 430.2 kB
  • After minification 416.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. Fonesquare images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 9.2 kB

  • Original 445.2 kB
  • After minification 445.2 kB
  • After compression 436.1 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.

CSS Optimization

-4%

Potential reduce by 9.0 kB

  • Original 220.5 kB
  • After minification 220.5 kB
  • After compression 211.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. Fonesquare.pk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 73 (88%)

Requests Now

83

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fonesquare.pk

www.fonesquare.pk

1600 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

579 ms

linearicons.min.css

linearicons.min.css

755 ms

style.min.css

style.min.css

763 ms

jquery.selectBox.css

jquery.selectBox.css

767 ms

font-awesome.css

font-awesome.css

771 ms

prettyPhoto.css

prettyPhoto.css

768 ms

style.css

style.css

917 ms

classic-themes.min.css

classic-themes.min.css

1010 ms

styles.css

styles.css

1018 ms

rs6.css

rs6.css

1037 ms

woocommerce.css

woocommerce.css

1025 ms

colorbox.css

colorbox.css

1028 ms

css

css

37 ms

ionicons.min.css

ionicons.min.css

1247 ms

eleganticons.min.css

eleganticons.min.css

1267 ms

font-awesome.min.css

font-awesome.min.css

1294 ms

bootstrap.min.css

bootstrap.min.css

1289 ms

style.css

style.css

1856 ms

photoswipe.min.css

photoswipe.min.css

1295 ms

default-skin.min.css

default-skin.min.css

1545 ms

tawc-deals.css

tawc-deals.css

1520 ms

frontend.css

frontend.css

1544 ms

front.css

front.css

1546 ms

js_composer.min.css

js_composer.min.css

1881 ms

jquery.min.js

jquery.min.js

1963 ms

jquery-migrate.min.js

jquery-migrate.min.js

1819 ms

rbtools.min.js

rbtools.min.js

2107 ms

rs6.min.js

rs6.min.js

2274 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

2083 ms

add-to-cart.min.js

add-to-cart.min.js

2124 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

2127 ms

waypoints.min.js

waypoints.min.js

2226 ms

front.js

front.js

2337 ms

js

js

73 ms

css

css

14 ms

jquery.selectBox.min.js

jquery.selectBox.min.js

2267 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

2266 ms

jquery.yith-wcwl.min.js

jquery.yith-wcwl.min.js

2267 ms

index.js

index.js

2348 ms

index.js

index.js

2061 ms

js.cookie.min.js

js.cookie.min.js

1886 ms

woocommerce.min.js

woocommerce.min.js

1993 ms

woocompare.min.js

woocompare.min.js

1988 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

2017 ms

underscore.min.js

underscore.min.js

2097 ms

wp-util.min.js

wp-util.min.js

2003 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

1997 ms

photoswipe.min.js

photoswipe.min.js

2047 ms

photoswipe-ui.min.js

photoswipe-ui.min.js

2035 ms

core.min.js

core.min.js

2029 ms

tooltip.min.js

tooltip.min.js

2062 ms

imagesloaded.min.js

imagesloaded.min.js

1922 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

1991 ms

jquery.fitvids.js

jquery.fitvids.js

2026 ms

isInViewport.min.js

isInViewport.min.js

2066 ms

jquery.coundown.js

jquery.coundown.js

2028 ms

jquery.counterup.min.js

jquery.counterup.min.js

1831 ms

jquery.tabs.js

jquery.tabs.js

1880 ms

nprogress.js

nprogress.js

1973 ms

slick.min.js

slick.min.js

2035 ms

notify.min.js

notify.min.js

1771 ms

scripts.js

scripts.js

1793 ms

tawc-deals.js

tawc-deals.js

1758 ms

instant_click.min.js

instant_click.min.js

1719 ms

frontend.js

frontend.js

1689 ms

cart-fragments.min.js

cart-fragments.min.js

1713 ms

js_composer_front.min.js

js_composer_front.min.js

1732 ms

forms.js

forms.js

1844 ms

frontend.js

frontend.js

1708 ms

ghbsawnuxc

ghbsawnuxc

294 ms

fbevents.js

fbevents.js

187 ms

fone-square-blue.jpg

fone-square-blue.jpg

1729 ms

projectors.jpg

projectors.jpg

1915 ms

js

js

137 ms

Iphone-14.jpg

Iphone-14.jpg

1873 ms

used-laptops-1.jpg

used-laptops-1.jpg

2119 ms

Graphics-tablet.jpg

Graphics-tablet.jpg

2250 ms

embed

embed

252 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8JoI3ZKyHqQg.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8JoI3ZKyHqQg.woff

1744 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBiEJo43ZKyHqQg.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBiEJo43ZKyHqQg.ttf

91 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBiEJo43ZKyHqQg.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBiEJo43ZKyHqQg.ttf

145 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBiEJo43ZKyHqQg.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBiEJo43ZKyHqQg.ttf

162 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBiEJo43ZKyHqQg.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBiEJo43ZKyHqQg.ttf

163 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBiEJo43ZKyHqQg.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBiEJo43ZKyHqQg.ttf

163 ms

init.js

init.js

187 ms

font

font

1641 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBiAJoI3ZKyHqQvhf.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBiAJoI3ZKyHqQvhf.woff

1899 ms

clarity.js

clarity.js

47 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8JoI3ZKyHqQg.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8JoI3ZKyHqQg.woff

2017 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBiEJoI3ZKyHqQvhf.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBiEJoI3ZKyHqQvhf.woff

1934 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBiAJoI3ZKyHqQvhf.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBiAJoI3ZKyHqQvhf.woff

1883 ms

bundle.js

bundle.js

11 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8JoI3ZKyHqQg.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8JoI3ZKyHqQg.woff

1971 ms

js

js

55 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBiEJoI3ZKyHqQvhf.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBiEJoI3ZKyHqQvhf.woff

2028 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBiAJoI3ZKyHqQvhf.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBiAJoI3ZKyHqQvhf.woff

1926 ms

ionicons.woff

ionicons.woff

2157 ms

ElegantIcons.woff

ElegantIcons.woff

2323 ms

fone-square-e1635665595188.jpg

fone-square-e1635665595188.jpg

1963 ms

c.gif

c.gif

7 ms

Accessibility Review

fonesquare.pk accessibility score

67

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-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

fonesquare.pk 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fonesquare.pk SEO score

91

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

High

Tap targets are not sized appropriately

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 Fonesquare.pk 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 Fonesquare.pk 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

fonesquare.pk

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