6.6 sec in total
2.6 sec
3.7 sec
305 ms
Click here to check amazing FPCT content. Otherwise, check out these important facts you probably never knew about fpct.or.tz
Worship is the fuel for discipleship. We are called to eat, drink, speak, think and work to the glory of God. We worship God by remembering the gospel through preaching, teaching, singing, praying and...
Visit fpct.or.tzWe analyzed Fpct.or.tz page load time and found that the first response time was 2.6 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
fpct.or.tz performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value8.7 s
1/100
25%
Value7.4 s
27/100
10%
Value340 ms
74/100
30%
Value0.067
97/100
15%
Value9.9 s
27/100
10%
2610 ms
195 ms
23 ms
170 ms
204 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 80% of them (64 requests) were addressed to the original Fpct.or.tz, 10% (8 requests) were made to Fonts.gstatic.com and 9% (7 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Fpct.or.tz.
Page size can be reduced by 2.4 MB (67%)
3.6 MB
1.2 MB
In fact, the total size of Fpct.or.tz main page is 3.6 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. 70% of websites need less resources to load. CSS take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 49.2 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 49.2 kB or 80% of the original size.
Potential reduce by 143.2 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. Obviously, FPCT needs image optimization as it can save up to 143.2 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 809.6 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 809.6 kB or 74% of the original size.
Potential reduce by 1.4 MB
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. Fpct.or.tz needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 89% of the original size.
Number of requests can be reduced by 47 (67%)
70
23
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FPCT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
fpct.or.tz
2610 ms
layerslider.css
195 ms
css
23 ms
styles.css
170 ms
settings.css
204 ms
css
35 ms
css
48 ms
css
49 ms
css
46 ms
css
43 ms
style.css
312 ms
js_composer.css
345 ms
select2.css
267 ms
bootstrap-theme.css
284 ms
bootstrap.css
365 ms
font-awesome.min.css
399 ms
base.css
560 ms
responsive.css
448 ms
owl.carousel.css
436 ms
wd_menu_front.css
458 ms
oswadmarket.css
539 ms
jquery.js
589 ms
jquery-migrate.min.js
526 ms
layerslider.kreaturamedia.jquery.js
605 ms
greensock.js
581 ms
layerslider.transitions.js
635 ms
jquery.themepunch.tools.min.js
685 ms
jquery.themepunch.revolution.min.js
699 ms
select2.js
726 ms
wd_menu_front.js
668 ms
jquery.hoverIntent.js
679 ms
css
14 ms
comment-reply.min.js
236 ms
jquery.form.min.js
286 ms
scripts.js
291 ms
TweenMax.js
371 ms
bootstrap.js
311 ms
jquery.ui.core.min.js
312 ms
jquery.ui.widget.min.js
370 ms
jquery.ui.tabs.min.js
397 ms
jquery.ui.mouse.min.js
397 ms
jquery.ui.accordion.min.js
421 ms
jquery.ui.effect.min.js
441 ms
jquery.touchSwipe.js
451 ms
include-script.js
534 ms
owl.carousel.min.js
483 ms
jquery.prettyPhoto.min.js
477 ms
jquery.prettyPhoto.init.min.js
509 ms
oswadmarket.js
541 ms
js_composer_front.js
549 ms
default-background.png
176 ms
Logofpct.png
445 ms
bg_menu.png
445 ms
top1.png
446 ms
Askofu-David-Batenzi1.jpg
447 ms
slide7.jpg
478 ms
slide1.jpg
499 ms
slide3.jpg
519 ms
slide6.jpg
549 ms
slide2.jpg
588 ms
mpangomkakati.jpg
509 ms
kaulimbiu.jpg
634 ms
fpctcentre.jpg
587 ms
eyecentre.jpg
657 ms
down.png
600 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
6 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
12 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
50 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
11 ms
EInbV5DfGHOiMmvb1Xr-hpS3E-kSBmtLoNJPDtbj2Pk.ttf
11 ms
fontawesome-webfont.woff
776 ms
shaw_down_menu.png
707 ms
bg-none.png
707 ms
o_button_prev.png
692 ms
o_button_next.png
720 ms
Zd2E9abXLFGSr9G3YK2MsMEHkXu385rSv8spHqOuvSI.ttf
20 ms
b9QBgL0iMZfDSpmcXcE8nBPtpc1JAjij63Hi_JcAPQ4.ttf
18 ms
b9QBgL0iMZfDSpmcXcE8nPVE82mBoqAQeMZO1WdebIw.ttf
18 ms
loader.gif
341 ms
ajax-loader.gif
415 ms
fpct.or.tz 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
fpct.or.tz 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
Page has valid source maps
fpct.or.tz 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
SW
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fpct.or.tz can be misinterpreted by Google and other search engines. Our service has detected that Swahili is used on the page, and it does not match the claimed English language. Our system also found out that Fpct.or.tz 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.
fpct.or.tz
Open Graph description is not detected on the main page of FPCT. 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: