8.3 sec in total
665 ms
7.3 sec
343 ms
Welcome to fbr.gov.pk homepage info - get ready to check FBR best content for Pakistan right away, or after learning these important things about fbr.gov.pk
FBR -Federal Board of Revenue is the Revenue Division of Government of Pakistan tasked with collecting taxes & duties and administrating relevant legislation.
Visit fbr.gov.pkWe analyzed Fbr.gov.pk page load time and found that the first response time was 665 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fbr.gov.pk performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value10.7 s
0/100
25%
Value10.3 s
8/100
10%
Value1,250 ms
19/100
30%
Value0.163
72/100
15%
Value19.2 s
2/100
10%
665 ms
1462 ms
35 ms
68 ms
115 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 16% of them (13 requests) were addressed to the original Fbr.gov.pk, 54% (43 requests) were made to Download1.fbr.gov.pk and 9% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Download1.fbr.gov.pk.
Page size can be reduced by 504.6 kB (12%)
4.3 MB
3.8 MB
In fact, the total size of Fbr.gov.pk main page is 4.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 75.9 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 16.6 kB, which is 18% 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 75.9 kB or 82% of the original size.
Potential reduce by 386.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. FBR images are well optimized though.
Potential reduce by 1.5 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.
Potential reduce by 40.7 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. Fbr.gov.pk needs all CSS files to be minified and compressed as it can save up to 40.7 kB or 77% of the original size.
Number of requests can be reduced by 16 (23%)
70
54
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FBR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fbr.gov.pk
665 ms
fbr.gov.pk
1462 ms
kh0j2du8cb
35 ms
js
68 ms
gtm.js
115 ms
roboto:n2,n4,n7,n3,n5:default.js
21 ms
css
858 ms
modernizr
847 ms
fbr.css
934 ms
clarity.js
8 ms
analytics.js
5 ms
collect
16 ms
font-awesome.min.css
32 ms
jquery
1531 ms
bootstrap
834 ms
collect
26 ms
ga-audiences
92 ms
FBR-Logo.png
1169 ms
FBRLatestUpdatesEng.png
1183 ms
arrow-news.png
1322 ms
income-tax-general-order-20240502.png
2474 ms
who-to-fbr-20240423.jpg
1891 ms
e-kachehri-chairman-fbr-20240422.png
2460 ms
fbr-balancesheet.png
2287 ms
tajir-dost-2024.png
2591 ms
06-pm-award--20240403.png
2723 ms
01-pm-award.png
2747 ms
02-pm-award.png
2851 ms
03-pm-award.png
3032 ms
04-pm-award.png
3053 ms
fm-2024.png
2877 ms
capital-assets-7e-guidlines.jpeg
3006 ms
FBR-Maloomat-02.jpeg
3035 ms
banner-22-v3.png
3136 ms
scam-alert.jpg
3161 ms
fbrhelpline.gif
3853 ms
fbr-info-logo.png
3319 ms
iris-logo-new.png
3319 ms
Weboc.png
3340 ms
FileIncomeTaxReturn.jpg
3417 ms
1-19-47d5ab7d-371a-448e-adf4-2f015612b4f3-national_sales_tax_banner2.png
3442 ms
FileGoodsDeclarations.jpg
3605 ms
e-payment.jpg
3602 ms
Income-Tax-Return-For-Year-2023.png
3628 ms
maloomat-fbr.png
3699 ms
1-19-4db08c95-6905-4742-b40d-ffe37d3b024b-FATF(2).jpg
3723 ms
hamonization.png
3887 ms
ftoaffairs.jpg
3892 ms
1-19-8431fc0b-ca4d-438d-8f04-12447f104e06-Tracktrace.jpg
3915 ms
1-19-1e7f117f-fb40-4cba-9b1c-bdba8124c487-HSTranspositionTable.png
3979 ms
budget-proposals-2024-25-20240223.png
4006 ms
ValuationofImmovablePropertiesSmall.jpg
4134 ms
EaseOfDoingBusiness.jpg
4172 ms
bg.jpg
286 ms
pral.png
304 ms
kh0j2du8cb
105 ms
cse.js
133 ms
ga.js
95 ms
sep.png
483 ms
MehrNastaliqWeb.woff
737 ms
fontawesome-webfont.woff
821 ms
glyphicons-halflings-regular.woff
790 ms
fontawesome-webfont.woff
27 ms
__utm.gif
20 ms
collect
23 ms
cse_element__en.js
13 ms
default+en.css
9 ms
default.css
13 ms
ga-audiences
70 ms
async-ads.js
76 ms
clear.png
54 ms
nav_logo114.png
9 ms
ExportFacilitationSchemes.jpg
3015 ms
POSIntegration2020.jpg
3026 ms
IncomeTaxVideoTutorial.jpg
2942 ms
taxassan.jpg
2402 ms
FBRtvcs.jpg
2134 ms
suplementary.jpg
2003 ms
dvidar.jpg
1994 ms
c.gif
7 ms
fbr.gov.pk accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
fbr.gov.pk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fbr.gov.pk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fbr.gov.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 Fbr.gov.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.
fbr.gov.pk
Open Graph description is not detected on the main page of FBR. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: