Access whatmobile.com.pk. Mobile phone prices - Pakistan's daily updated mobile phone prices Pakistan What Mobile

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value2,460 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.255

48/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

whatmobile.com.pk

293 ms

www.whatmobile.com.pk

1821 ms

OneSignalSDK.js

2423 ms

plusone.js

3148 ms

style.css

1801 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 52% of them (55 requests) were addressed to the original Whatmobile.com.pk, 12% (13 requests) were made to Apis.google.com and 6% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (15.2 sec) relates to the external source Bs.serving-sys.com.

Content Size

3.4 MB

After Optimization

1.3 MB

In fact, the total size of Whatmobile.com.pk main page is 3.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-96%

Potential reduce by 883.5 kB

Original 917.5 kB
After minification 511.3 kB
After compression 34.0 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 406.3 kB, which is 44% 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 883.5 kB or 96% of the original size.

Image Optimization

-8%

Potential reduce by 46.9 kB

Original 560.4 kB
After minification 513.5 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. What Mobile images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 1.2 MB

Original 1.9 MB
After minification 1.9 MB
After compression 717.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 1.2 MB or 62% of the original size.

CSS Optimization

-84%

Potential reduce by 10.7 kB

Original 12.7 kB
After minification 10.9 kB
After compression 2.1 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. Whatmobile.com.pk needs all CSS files to be minified and compressed as it can save up to 10.7 kB or 84% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

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.

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

High

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatmobile.com.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 Whatmobile.com.pk main page’s claimed encoding is iso-8859-1. 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

whatmobile.com.pk

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Mobile phone prices - Pakistan's daily updated mobile phone prices Pakistan What Mobile

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

whatmobile.com.pk

www.whatmobile.com.pk

OneSignalSDK.js

plusone.js

style.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

whatmobile.com.pk

www.whatmobile.com.pk

OneSignalSDK.js

plusone.js

style.css

ajax-loader.gif

adsbygoogle.js

swfobject.js

header-Left-new.gif

SamsungGalaxyNote8-s.jpg

6s.jpg

HuaweiY7Prime-s.jpg

SamsungGalaxyJ7Core-s.jpg

5ss.jpg

OppoA71-s.jpg

TecnoPhantom6Plus-s.jpg

OppoF3Plus-s.jpg

SamsungGalaxyJ7Pro-s.jpg

Mate9Blacks.jpg

GalaxyS8Pluss.jpg

UPlayss.jpg

VivoY69-s.jpg

SamsungGalaxyJ5Pro-s.jpg

VivoV5s-s.jpg

OppoF3Black-s.jpg

MeizuMX6-s.jpg

NoirM6s.jpg

TecnoPhantom6-s.jpg

TecnoCamonCXAir-s.jpg

TecnoCamonCX-s.jpg

QmobileNoirCS1Plus-s.jpg

InfinixNote4-s.jpg

QmobileNoirX1S-s.jpg

TecnoL8Lite-s.jpg

QmobileEvokPowerLite-s.jpg

QmobileEvokPower-s.jpg

QmobileNoirJ2-s.jpg

QmobileQNote-s.jpg

HaierG55-s.jpg

QmobileNoirLT550-s.jpg

QmobileDualOne-s.jpg

InfinixSmart-s.jpg

QmobileNoirJ1-s.jpg