7.9 sec in total
42 ms
7.5 sec
377 ms
Visit pt.witness.org now to see the best up-to-date Pt Witness content for United States and also check out these interesting facts you probably never knew about pt.witness.org
Visit pt.witness.orgWe analyzed Pt.witness.org page load time and found that the first response time was 42 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pt.witness.org performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value8.2 s
2/100
25%
Value7.1 s
31/100
10%
Value730 ms
40/100
30%
Value0.002
100/100
15%
Value7.8 s
44/100
10%
42 ms
904 ms
62 ms
2888 ms
1149 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pt.witness.org, 71% (39 requests) were made to Portugues.witness.org and 13% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.5 sec) relates to the external source Portugues.witness.org.
Page size can be reduced by 1.7 MB (50%)
3.4 MB
1.7 MB
In fact, the total size of Pt.witness.org main page is 3.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 21.7 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 21.7 kB or 78% of the original size.
Potential reduce by 4.4 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. Pt Witness images are well optimized though.
Potential reduce by 664.1 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 664.1 kB or 71% of the original size.
Potential reduce by 988.8 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. Pt.witness.org needs all CSS files to be minified and compressed as it can save up to 988.8 kB or 91% of the original size.
Number of requests can be reduced by 33 (72%)
46
13
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pt Witness. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
pt.witness.org
42 ms
portugues.witness.org
904 ms
css
62 ms
portugues.witness.org
2888 ms
layerslider.css
1149 ms
css
83 ms
style.css
1147 ms
jss-style.min.css
1153 ms
style.css
1150 ms
font-awesome.min.css
1150 ms
stylesheet.min.css
1659 ms
js_composer.css
1706 ms
style_dynamic.php
2415 ms
responsive.min.css
2016 ms
style_dynamic_responsive.php
2896 ms
custom_css.php
5025 ms
style.css
2243 ms
jetpack.css
2421 ms
greensock.js
2908 ms
jquery.js
2911 ms
jquery-migrate.min.js
3153 ms
layerslider.kreaturamedia.jquery.js
3164 ms
layerslider.transitions.js
3171 ms
script.js
3175 ms
jss-script.min.js
3176 ms
devicepx-jetpack.js
32 ms
qode-like.js
3215 ms
plugins.js
3263 ms
default_dynamic.php
6458 ms
default.min.js
3225 ms
custom_js.php
6321 ms
comment-reply.min.js
3272 ms
js_composer_front.js
3277 ms
e-201611.js
34 ms
wp-emoji-release.min.js
3270 ms
style.css
1089 ms
ga.js
126 ms
witness_logo.png
186 ms
bulldozer_2.jpg
177 ms
egypt.jpg
178 ms
hands_new.jpg
164 ms
arrow.png
120 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
119 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
124 ms
5M21SdFLkD52QavfmHs6cA.ttf
147 ms
Pru33qjShpZSmG3z6VYwnaCWcynf_cDxXwCLxiixG1c.ttf
157 ms
fontawesome-webfont.woff
172 ms
AWM5wXtMJeRP-AcRTgT4qQ.ttf
157 ms
l1cOQ90roY9yC7voEhngDKCWcynf_cDxXwCLxiixG1c.ttf
157 ms
dI-qzxlKVQA6TUC5RKSb36CWcynf_cDxXwCLxiixG1c.ttf
156 ms
__utm.gif
38 ms
social_share.png
46 ms
social_share_white.png
49 ms
logo.png
50 ms
g.gif
19 ms
pt.witness.org 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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pt.witness.org 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
Missing source maps for large first-party JavaScript
pt.witness.org SEO score
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
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pt.witness.org can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Pt.witness.org 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.
pt.witness.org
Open Graph description is not detected on the main page of Pt Witness. 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: