hbl.com.pk

hbl.com.pk is SSL secured

Free website and domain report on hbl.com.pk

Last Updated: 5th August, 2020 Update Now
Overview

Snoop Summary for hbl.com.pk

This is a free and comprehensive report about hbl.com.pk. Hbl.com.pk is hosted in United States on a server with an IP address of 34.70.88.8, where USD is the local currency and the local language is English. Hbl.com.pk has the potential to be earning an estimated $1 USD per day from advertising revenue. If hbl.com.pk was to be sold it would possibly be worth $751 USD (based on the daily revenue potential of the website over a 24 month period). Hbl.com.pk receives an estimated 356 unique visitors every day - a decent amount of traffic! This report was last updated 5th August, 2020.

About hbl.com.pk

Site Preview: hbl.com.pk hbl.com.pk
Title:
Description:
Keywords and Tags: parked domain
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$751 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,635,051
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 356
Monthly Visitors: 10,836
Yearly Visitors: 129,940
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $31 USD
Yearly Revenue: $370 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: hbl.com.pk 10
Domain Name: hbl 3
Extension (TLD): compk 5

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 73
Performance 90
Accessibility 81
Best Practices 85
SEO 64
Progressive Web App 44
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
90

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for hbl.com.pk. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.2 s
The timing of the largest text or image that is painted.
Time to Interactive — 2.1 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 2.0 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 20 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive hbl.com.pk as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://hbl.com.pk/
0
100.04900000058
202
0
302
text/plain
https://hbl.com.pk/
100.34700005781
252.312000026
31498
31014
200
text/html
Document
https://fonts.googleapis.com/css?family=Poppins:400,500,700&display=swap
269.43700003903
286.11600003205
1566
3726
200
text/css
Stylesheet
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
269.70200007781
392.1819999814
31816
191420
200
text/css
Stylesheet
https://www.google.com/recaptcha/api.js?render=6LfNXOYUAAAAAORM8NxKpSR93I7ItGRjlJXEfhcR
269.97000002302
307.24900006317
1376
708
200
text/javascript
Script
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
270.63400007319
420.65300000831
171624
508320
200
application/javascript
Script
https://hbl.com.pk/dist/app_pages.js
271.01100003347
548.76700008754
301398
301170
200
application/javascript
Script
https://cdn.fodn.com/pages/dist/particles.js?v=1.0.0.0.6
271.35900000576
443.27599997632
7080
22653
200
application/javascript
Script
https://cdn.fodn.com/pages/dist/transaction-general.js?v=1.0.0.0.6
271.51600003708
444.98500006739
1725
2923
200
application/javascript
Script
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/recaptcha__en.js
447.20300007612
458.85699999053
133603
337174
200
text/javascript
Script
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
522.04900002107
714.11300008185
31816
65536
200
text/css
Image
https://fonts.gstatic.com/s/poppins/v12/pxiByp8kv8JHgFVrLCz7Z1xlFd2JQEk.woff2
525.57200007141
531.03900002316
8426
7832
200
font/woff2
Font
https://fonts.gstatic.com/s/poppins/v12/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
533.49399997387
535.82900005858
8494
7900
200
font/woff2
Font
https://hbl.com.pk/domainsForSale
668.0949999718
833.30300007947
11102
10941
200
application/json
XHR
https://cdn.fodn.com/pages/dist/icons/fonts/icomoon.ttf?el2i04
696.97100005578
771.17100008763
4441
3492
200
binary/octet-stream
Font
758.09500005562
758.13099998049
0
384
200
image/svg+xml
Image
760.1250000298
760.15900005586
0
383
200
image/svg+xml
Image
762.24399998318
762.29099999182
0
403
200
image/svg+xml
Image
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LfNXOYUAAAAAORM8NxKpSR93I7ItGRjlJXEfhcR&co=aHR0cHM6Ly9oYmwuY29tLnBrOjQ0Mw..&hl=en&v=AFBwIe6h0oOL7MOVu88LHld-&size=invisible&cb=2n16jjibzkpj
779.13699997589
820.39200002328
10451
19493
200
text/html
Document
https://cdn.fodn.com/pages/assets/logos/5f01418dc0ff37000137e14b.jpg
1001.8610000843
1028.6959999939
17075
16461
200
image/jpeg
Image
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
1002.0510000177
1069.5159999887
18706
18092
200
image/jpeg
Image
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
1007.426999975
1078.4850000637
21534
20920
200
image/jpeg
Image
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/styles__ltr.css
1111.5010000067
1121.143000084
25883
50696
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/recaptcha__en.js
1111.9350000517
1122.3839999875
133603
337174
200
text/javascript
Script
https://www.google.com/js/bg/Tt0mLDKZlf_cow3Xat8Z87ITm0Gj_eaE9na0fCfZ4RQ.js
1209.9050000543
1213.3540000068
6132
12511
200
text/javascript
Script
https://www.google.com/recaptcha/api2/webworker.js?hl=en&v=AFBwIe6h0oOL7MOVu88LHld-
1256.4390000189
1270.5120000755
932
102
200
text/javascript
Other
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
285.355
9.212
423.178
8.192
476.545
93.28
569.858
5.313
581.644
7.448
598.164
26.307
626.763
94.063
720.903
22.417
744.429
69.674
814.353
28.361
846.06
43.9
891.021
30.384
922.001
7.394
929.431
108.12
1037.881
36.426
1075.022
26.47
1105.361
15.101
1121.359
16.679
1141.152
15.906
1161.465
13.424
1176.074
15.029
1191.482
75.027
1267.678
15.006
1289.19
13.339
1302.544
124.52
1427.223
21.625
1448.883
14.406
1463.326
23.428
1487.036
78.488
1566.767
14.261
1581.274
14.288
1601.544
11.844
1613.508
15.869
1629.62
11.661
1641.401
15.22
1656.659
6.639
1664.522
13.887
1678.451
6.82
1692.396
16.756
1709.193
10.762
1719.982
11.241
1733.449
16.248
1753.389
17.009
1775.518
13.121
1789.302
13.73
1803.081
14.49
1817.588
14.177
1844.417
13.209
1865.396
13.837
1887.381
20.676
1908.914
14.828
1923.798
7.784
1932.204
16.205
1955.808
14.263
1976.116
14.503
1997.094
13.467
2015.153
14.932
2035.726
16.305
2053.914
12.944
2072.13
24.117
2109.276
14.3
2127.958
12.747
2144.854
14.61
2165.335
13.738
2187.002
14.109
2201.139
5.182
2206.356
13.6
2220.43
48.075
2269.169
12.823
2284.082
14.53
2299.052
15.657
2318.897
12.285
2332.404
13.153
2353.505
15.804
2373.856
13.216
2392.422
14.457
2411.768
13.345
2430.755
13.249
2448.206
13.743
2467.101
11.411
2483.877
14.682
2502.819
14.779
2522.498
12.549
2540.422
13.474
2559.1
14.041
2577.337
12.768
2594.085
17.427
2612.587
19.762
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 32 KiB
Images can slow down the page's load time. Hbl.com.pk should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
20920
12346
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
18092
10677
https://cdn.fodn.com/pages/assets/logos/5f01418dc0ff37000137e14b.jpg
16461
9714
Defer offscreen images — Potential savings of 38 KiB
Time to Interactive can be slowed down by resources on the page. Hbl.com.pk should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
20920
20920
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
18092
18092
Minify CSS — Potential savings of 2 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Hbl.com.pk should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
.according-card, .dark-contrast .according-card { -webkit-box-shadow: 0 .75rem 1.5rem rgba(255, ... } ...
9711
2501
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Hbl.com.pk should consider minifying JS files.
Remove unused CSS — Potential savings of 107 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Hbl.com.pk should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
92929
83203
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/styles__ltr.css
25883
25883
Efficiently encode images — Potential savings of 39 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
20920
14986
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
18092
12779
https://cdn.fodn.com/pages/assets/logos/5f01418dc0ff37000137e14b.jpg
16461
11797
Serve images in next-gen formats — Potential savings of 46 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
20920
17650
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
18092
15466
https://cdn.fodn.com/pages/assets/logos/5f01418dc0ff37000137e14b.jpg
16461
14137
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 150 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Hbl.com.pk should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://hbl.com.pk/
0
https://hbl.com.pk/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Hbl.com.pk should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 958 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://hbl.com.pk/dist/app_pages.js
301398
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
171624
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/recaptcha__en.js
133603
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/recaptcha__en.js
133603
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
31816
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
31816
https://hbl.com.pk/
31498
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/styles__ltr.css
25883
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
21534
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
18706
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Hbl.com.pk should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://hbl.com.pk/
526.309
28.511
1.277
https://cdn.fodn.com/pages/dist/particles.js?v=1.0.0.0.6
454.421
284.734
1.482
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
306.97
160.571
8.729
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/recaptcha__en.js
290.098
242.943
17.57
https://hbl.com.pk/dist/app_pages.js
179.978
156.99
5.889
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LfNXOYUAAAAAORM8NxKpSR93I7ItGRjlJXEfhcR&co=aHR0cHM6Ly9oYmwuY29tLnBrOjQ0Mw..&hl=en&v=AFBwIe6h0oOL7MOVu88LHld-&size=invisible&cb=2n16jjibzkpj
176.758
163.931
1.441
Minimizes main-thread work — 2.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1059.521
Rendering
536.014
Style & Layout
150.331
Other
141.047
Garbage Collection
63.072
Script Parsing & Compilation
38.478
Parse HTML & CSS
24.757
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 23 requests • 958 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
23
980483
Script
8
756541
Image
4
89131
Stylesheet
3
59265
Document
2
41949
Font
3
21361
Other
3
12236
Media
0
0
Third-party
19
636283
Minimize third-party usage — Third-party code blocked the main thread for 70 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
293089
72.905
18891
0
18486
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00070371100746573
0.00036935701337841
0.00017536686608594
0.00014001684594054
5.6249100402214E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 5 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/recaptcha__en.js
2005
125
https://hbl.com.pk/dist/app_pages.js
1816
108
https://hbl.com.pk/dist/app_pages.js
1612
94
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/recaptcha__en.js
2171
78
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/recaptcha__en.js
1930
75

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.
Total Blocking Time — 180 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First Meaningful Paint — 1.3 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 520 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Hbl.com.pk should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Poppins:400,500,700&display=swap
1566
230
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
31816
310
https://www.google.com/recaptcha/api.js?render=6LfNXOYUAAAAAORM8NxKpSR93I7ItGRjlJXEfhcR
1376
230
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
171624
470
Remove unused JavaScript — Potential savings of 345 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://hbl.com.pk/dist/app_pages.js
301398
206232
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
171624
77019
https://www.gstatic.com/recaptcha/releases/AFBwIe6h0oOL7MOVu88LHld-/recaptcha__en.js
133603
69885
Enable text compression — Potential savings of 246 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://hbl.com.pk/dist/app_pages.js
301170
216720
https://hbl.com.pk/
31014
25139
https://hbl.com.pk/domainsForSale
10941
9634

Diagnostics

Serve static assets with an efficient cache policy — 10 resources found
Hbl.com.pk can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://hbl.com.pk/dist/app_pages.js
0
301398
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
2592000000
171624
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
2592000000
31816
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
2592000000
31816
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
2592000000
21534
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
2592000000
18706
https://cdn.fodn.com/pages/assets/logos/5f01418dc0ff37000137e14b.jpg
2592000000
17075
https://cdn.fodn.com/pages/dist/particles.js?v=1.0.0.0.6
2592000000
7080
https://cdn.fodn.com/pages/dist/icons/fonts/icomoon.ttf?el2i04
2592000000
4441
https://cdn.fodn.com/pages/dist/transaction-general.js?v=1.0.0.0.6
2592000000
1725
Avoid an excessive DOM size — 1,418 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
1,418
Maximum DOM Depth
20
Maximum Child Elements
81
81

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of hbl.com.pk. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Hbl.com.pk may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Hbl.com.pk may provide relevant information that dialogue cannot, by using audio descriptions.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Document doesn't have a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that hbl.com.pk should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.4.1
jQuery
3.4.1
Vue
2.5.17
core-js
2.6.5: pure, 2.6.5: global, 2.6.11: global
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://hbl.com.pk/
Includes front-end JavaScript libraries with known security vulnerabilities — 2 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
2
Medium
64

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for hbl.com.pk. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hbl.com.pk on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Content Best Practices

Document doesn't have a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Failing Elements
Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
44

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of hbl.com.pk. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hbl.com.pk on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://hbl.com.pk/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 65
Performance 43
Accessibility 81
Best Practices 85
SEO 69
Progressive Web App 46
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://hbl.com.pk/
Updated: 5th August, 2020

5.68 seconds
First Contentful Paint (FCP)
9%
22%
69%

0.05 seconds
First Input Delay (FID)
88%
9%
3%

Simulate loading on mobile
43

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for hbl.com.pk. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Cumulative Layout Shift — 0.019
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Hbl.com.pk should consider serving more appropriate-sized images.
Minify CSS — Potential savings of 2 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Hbl.com.pk should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
.according-card, .dark-contrast .according-card { -webkit-box-shadow: 0 .75rem 1.5rem rgba(255, ... } ...
9711
2501
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Hbl.com.pk should consider minifying JS files.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 120 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Hbl.com.pk should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://hbl.com.pk/
0
https://hbl.com.pk/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Hbl.com.pk should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 958 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://hbl.com.pk/dist/app_pages.js
301398
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
171624
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/recaptcha__en.js
133869
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/recaptcha__en.js
133869
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
31816
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
31816
https://hbl.com.pk/
31498
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/styles__ltr.css
25883
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
21534
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
18706
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Hbl.com.pk should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 23 requests • 958 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
23
981324
Script
8
757045
Image
4
89131
Stylesheet
3
59248
Document
2
42298
Font
3
21360
Other
3
12242
Media
0
0
Third-party
19
637109
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.016933376736111
0.0012109325318852
0.001006747536088
|
0.00020492735390181
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 15 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/recaptcha__en.js
8557
453
https://hbl.com.pk/dist/app_pages.js
7290
357
https://hbl.com.pk/dist/app_pages.js
7977
314
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/recaptcha__en.js
9091
254
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/recaptcha__en.js
8310
247
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
5802
211
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
5340
168
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LfNXOYUAAAAAORM8NxKpSR93I7ItGRjlJXEfhcR&co=aHR0cHM6Ly9oYmwuY29tLnBrOjQ0Mw..&hl=en&v=IU7gZ7o6RDdDE6U4Y1YJJWnN&size=invisible&cb=4j6lmsl4uzd2
6382
141
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
5562
92
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/recaptcha__en.js
5654
89
https://www.google.com/js/bg/Tt0mLDKZlf_cow3Xat8Z87ITm0Gj_eaE9na0fCfZ4RQ.js
9010
81
https://cdn.fodn.com/pages/dist/particles.js?v=1.0.0.0.6
3186
80
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LfNXOYUAAAAAORM8NxKpSR93I7ItGRjlJXEfhcR&co=aHR0cHM6Ly9oYmwuY29tLnBrOjQ0Mw..&hl=en&v=IU7gZ7o6RDdDE6U4Y1YJJWnN&size=invisible&cb=4j6lmsl4uzd2
6051
59
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
5743
58
https://cdn.fodn.com/pages/dist/particles.js?v=1.0.0.0.6
2979
57

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://hbl.com.pk/
0
69.484999999986
217
0
302
text/plain
https://hbl.com.pk/
69.784999999683
183.88200000481
31498
31014
200
text/html
Document
https://fonts.googleapis.com/css?family=Poppins:400,500,700&display=swap
196.35299999936
210.80000000075
1549
3726
200
text/css
Stylesheet
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
196.53200000175
235.18200000399
31816
191420
200
text/css
Stylesheet
https://www.google.com/recaptcha/api.js?render=6LfNXOYUAAAAAORM8NxKpSR93I7ItGRjlJXEfhcR
196.88999999926
222.59400000621
1348
708
200
text/javascript
Script
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
197.25000000471
258.96300000022
171624
508320
200
application/javascript
Script
https://hbl.com.pk/dist/app_pages.js
197.61300000391
350.75200000574
301398
301170
200
application/javascript
Script
https://cdn.fodn.com/pages/dist/particles.js?v=1.0.0.0.6
197.89100000344
260.30800000444
7080
22653
200
application/javascript
Script
https://cdn.fodn.com/pages/dist/transaction-general.js?v=1.0.0.0.6
198.06700000481
263.33400000294
1725
2923
200
application/javascript
Script
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/recaptcha__en.js
278.9630000043
288.49000000628
133869
339652
200
text/javascript
Script
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
346.30599999946
379.61300000461
31816
65536
200
text/css
Image
https://fonts.gstatic.com/s/poppins/v12/pxiByp8kv8JHgFVrLCz7Z1xlFd2JQEk.woff2
349.27600000083
353.83900000306
8425
7832
200
font/woff2
Font
https://fonts.gstatic.com/s/poppins/v12/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
356.20400000334
359.11100000521
8494
7900
200
font/woff2
Font
https://hbl.com.pk/domainsForSale
447.48600000457
502.22300000314
11102
10941
200
application/json
XHR
https://cdn.fodn.com/pages/dist/icons/fonts/icomoon.ttf?el2i04
477.74200000276
493.33200000547
4441
3492
200
binary/octet-stream
Font
522.74600000237
522.7870000017
0
384
200
image/svg+xml
Image
525.324000002
525.450000001
0
383
200
image/svg+xml
Image
528.0980000025
528.14500000386
0
403
200
image/svg+xml
Image
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LfNXOYUAAAAAORM8NxKpSR93I7ItGRjlJXEfhcR&co=aHR0cHM6Ly9oYmwuY29tLnBrOjQ0Mw..&hl=en&v=IU7gZ7o6RDdDE6U4Y1YJJWnN&size=invisible&cb=4j6lmsl4uzd2
583.75599999999
619.02499999997
10800
20253
200
text/html
Document
https://cdn.fodn.com/pages/assets/logos/5f01418dc0ff37000137e14b.jpg
694.22000000486
720.82400000363
17075
16461
200
image/jpeg
Image
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
694.45900000574
711.58200000355
18706
18092
200
image/jpeg
Image
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
694.89100000646
760.20500000595
21534
20920
200
image/jpeg
Image
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/styles__ltr.css
895.01100000052
902.5810000021
25883
50696
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/recaptcha__en.js
895.2780000036
948.82200000575
133869
339652
200
text/javascript
Script
https://www.google.com/js/bg/Tt0mLDKZlf_cow3Xat8Z87ITm0Gj_eaE9na0fCfZ4RQ.js
1006.4580000035
1010.5949999997
6132
12511
200
text/javascript
Script
https://www.google.com/recaptcha/api2/webworker.js?hl=en&v=IU7gZ7o6RDdDE6U4Y1YJJWnN
1045.3039999993
1063.6430000013
923
102
200
text/javascript
Other
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
214.752
7.495
265.03
7.106
307.513
84.066
402.221
5.312
411.629
89.2
501.045
22.386
523.555
46.247
569.966
44.687
615.648
29.233
644.914
78.554
725.319
105.708
832.466
19.007
851.503
14.863
872.587
17.807
891.392
20.229
912.949
9.875
924.473
9.739
936.066
10.008
951.964
10.347
968.654
10.855
985.341
10.182
998.896
61.63
1060.558
10.762
1076.111
11.859
1088.41
11.336
1100.162
113.184
1215.992
12.063
1228.085
20.312
1248.558
63.614
1313.114
10.951
1324.253
10.653
1335.47
11.836
1347.669
14.356
1362.571
11.951
1375.078
12.063
1390.296
10.902
1401.229
12.31
1413.581
5.492
1419.087
13.435
1433.713
11.257
1445.014
6.126
1451.246
10.98
1462.435
10.387
1473.033
11.337
1485.369
12.144
1502.024
12.076
1514.149
11.534
1526.323
11.349
1537.735
35.321
1573.073
9.61
1584.943
9.798
1596.265
9.395
1609.404
11.283
1622.271
9.063
1635.304
10.636
1652.472
9.335
1661.841
5.925
1668.634
9.295
1685.39
11.01
1701.992
11.072
1718.622
11.313
1735.403
10.455
1752.022
9.486
1768.716
10.109
1785.415
10.907
1802.023
10.372
1818.679
11.244
1835.325
14.273
1852.057
9.45
1868.64
10.027
1885.407
10.993
1902.038
10.549
1918.633
11.767
1935.38
20.08
1955.644
10.492
1968.621
9.52
1985.366
10.36
2001.982
10.145
2018.637
12.018
2035.365
11.045
2051.987
10.712
2068.724
11.358
2085.355
9.289
2102.316
10.044
2118.632
11.085
2135.307
10.222
2152.022
9.703
2168.634
9.779
2185.28
12.075
2202.263
10.373
2218.614
10.276
2235.29
9.986
2251.974
9.883
2268.59
9.713
2285.266
9.215
2301.993
10.734
2318.621
10.66
2335.296
10.087
2351.942
10.901
2368.643
10.742
2385.337
12.027
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 3.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 4.1 s
The time taken for the page contents to be visibly populated.

Opportunities

Defer offscreen images — Potential savings of 54 KiB
Time to Interactive can be slowed down by resources on the page. Hbl.com.pk should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
20920
20920
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
18092
18092
https://cdn.fodn.com/pages/assets/logos/5f01418dc0ff37000137e14b.jpg
16461
16461
Remove unused CSS — Potential savings of 107 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Hbl.com.pk should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
92929
83687
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/styles__ltr.css
25883
25883
Efficiently encode images — Potential savings of 39 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
20920
14986
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
18092
12779
https://cdn.fodn.com/pages/assets/logos/5f01418dc0ff37000137e14b.jpg
16461
11797
Serve images in next-gen formats — Potential savings of 46 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
20920
17650
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
18092
15466
https://cdn.fodn.com/pages/assets/logos/5f01418dc0ff37000137e14b.jpg
16461
14137

Diagnostics

Reduce JavaScript execution time — 3.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://hbl.com.pk/
2519.992
74.12
3.992
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
1323.796
623.288
29.42
https://cdn.fodn.com/pages/dist/particles.js?v=1.0.0.0.6
1013.86
444.74
4.748
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/recaptcha__en.js
998.276
885.076
53.736
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LfNXOYUAAAAAORM8NxKpSR93I7ItGRjlJXEfhcR&co=aHR0cHM6Ly9oYmwuY29tLnBrOjQ0Mw..&hl=en&v=IU7gZ7o6RDdDE6U4Y1YJJWnN&size=invisible&cb=4j6lmsl4uzd2
686.376
503.984
5.676
https://hbl.com.pk/dist/app_pages.js
576.292
537.848
17.528
Unattributable
147.36
6.324
0.808
https://www.google.com/js/bg/Tt0mLDKZlf_cow3Xat8Z87ITm0Gj_eaE9na0fCfZ4RQ.js
77.216
70.512
5.58

Metrics

Largest Contentful Paint — 4.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 9.0 s
The time taken for the page to become fully interactive.
Total Blocking Time — 1,560 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 8.6 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 450 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 5.5 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 190 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive hbl.com.pk as laggy when the latency is higher than 0.05 seconds.
First Contentful Paint (3G) — 7708.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 2,150 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Hbl.com.pk should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Poppins:400,500,700&display=swap
1549
780
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
31816
1230
https://www.google.com/recaptcha/api.js?render=6LfNXOYUAAAAAORM8NxKpSR93I7ItGRjlJXEfhcR
1348
780
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
171624
1980
Remove unused JavaScript — Potential savings of 343 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://hbl.com.pk/dist/app_pages.js
301398
206232
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
171624
77019
https://www.gstatic.com/recaptcha/releases/IU7gZ7o6RDdDE6U4Y1YJJWnN/recaptcha__en.js
133869
67767
Enable text compression — Potential savings of 246 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://hbl.com.pk/dist/app_pages.js
301170
216720
https://hbl.com.pk/
31014
25144
https://hbl.com.pk/domainsForSale
10941
9639

Diagnostics

Serve static assets with an efficient cache policy — 10 resources found
Hbl.com.pk can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://hbl.com.pk/dist/app_pages.js
0
301398
https://cdn.fodn.com/pages/dist/app.js?v=1.0.0.0.6
2592000000
171624
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
2592000000
31816
https://cdn.fodn.com/pages/dist/app.css?v=1.0.0.0.6
2592000000
31816
https://cdn.fodn.com/pages/assets/logos/5f0140d7c0ff37000137e0fd.jpg
2592000000
21534
https://cdn.fodn.com/pages/assets/logos/5f01411cc0ff37000137e11b.jpg
2592000000
18706
https://cdn.fodn.com/pages/assets/logos/5f01418dc0ff37000137e14b.jpg
2592000000
17075
https://cdn.fodn.com/pages/dist/particles.js?v=1.0.0.0.6
2592000000
7080
https://cdn.fodn.com/pages/dist/icons/fonts/icomoon.ttf?el2i04
2592000000
4441
https://cdn.fodn.com/pages/dist/transaction-general.js?v=1.0.0.0.6
2592000000
1725
Avoid an excessive DOM size — 1,418 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
1,418
Maximum DOM Depth
20
Maximum Child Elements
81
Minimize main-thread work — 7.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
3150.448
Rendering
2531.564
Style & Layout
781.912
Other
541.38
Garbage Collection
181.52
Script Parsing & Compilation
123.856
Parse HTML & CSS
79.156
Reduce the impact of third-party code — Third-party code blocked the main thread for 700 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
293621
595.064
19203
103.944
18468
0
81

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of hbl.com.pk. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Hbl.com.pk may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Hbl.com.pk may provide relevant information that dialogue cannot, by using audio descriptions.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Document doesn't have a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that hbl.com.pk should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.4.1
jQuery
3.4.1
Vue
2.5.17
core-js
2.6.5: pure, 2.6.5: global, 2.6.11: global
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://hbl.com.pk/
Includes front-end JavaScript libraries with known security vulnerabilities — 2 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
2
Medium
69

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for hbl.com.pk. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hbl.com.pk on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Content Best Practices

Document doesn't have a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Failing Elements
Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
46

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of hbl.com.pk. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of hbl.com.pk on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://hbl.com.pk/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 34.70.88.8
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Google LLC
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: hbl.com.pk
Issued By: Let's Encrypt Authority X3
Valid From: 15th June, 2020
Valid To: 13th September, 2020
Subject: CN = hbl.com.pk
Hash: 85ed0ebf
Issuer: CN = Let's Encrypt Authority X3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03FA9082D7171CD0C3C9DDD3B54478565664
Serial Number (Hex): 03FA9082D7171CD0C3C9DDD3B54478565664
Valid From: 15th June, 2024
Valid To: 13th September, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://ocsp.int-x3.letsencrypt.org
CA Issuers - URI:http://cert.int-x3.letsencrypt.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E7:12:F2:B0:37:7E:1A:62:FB:8E:C9:0C:61:84:F1:EA:
7B:37:CB:56:1D:11:26:5B:F3:E0:F3:4B:F2:41:54:6E
Timestamp : Jun 15 10:03:54.963 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:0E:30:F7:BB:87:2F:2C:4F:0F:C3:A8:5B:
53:E9:F9:AF:63:F2:04:DE:D9:0E:20:03:26:C5:DA:92:
21:A7:3D:F9:02:21:00:DE:27:86:C2:A2:C5:7D:90:82:
01:19:03:F8:13:95:E6:02:60:66:AD:1A:8A:83:B4:B8:
44:90:E7:59:6F:BA:80
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
Timestamp : Jun 15 10:03:55.009 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:4B:FE:A3:E6:39:48:26:68:7C:B2:D3:12:
74:A1:A4:DC:DE:2C:6B:AD:CF:28:54:AF:12:1F:E4:F7:
A9:1B:A8:1F:02:20:08:3C:0D:F0:ED:64:41:33:05:3A:
99:A5:52:5A:C3:07:2A:00:28:80:A1:54:37:54:1A:06:
87:16:7C:81:4F:15
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:hbl.com.pk
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Cache-Control: no-cache, no-store
Content-Type: text/html; charset=utf-8
Date: 5th August, 2020
Server: Kestrel
Pragma: no-cache
Set-Cookie: *
X-Frame-Options: SAMEORIGIN

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers:
Full Whois: hbl.com.pk domain is not supported

Nameservers

Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$13,887 USD 3/5
$84,883 USD 3/5
$13,471 USD 3/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$23,762 USD 2/5
0/5
$991 USD 1/5
$705 USD
0/5

Sites hosted on the same IP address