2.3 sec in total
157 ms
1.9 sec
194 ms
Visit phabricator.com now to see the best up-to-date Phabricator content for Poland and also check out these interesting facts you probably never knew about phabricator.com
Visit phabricator.comWe analyzed Phabricator.com page load time and found that the first response time was 157 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
phabricator.com performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value4.7 s
33/100
25%
Value4.0 s
80/100
10%
Value300 ms
78/100
30%
Value0.046
99/100
15%
Value5.5 s
71/100
10%
157 ms
487 ms
301 ms
315 ms
319 ms
Our browser made a total of 17 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Phabricator.com, 71% (12 requests) were made to P.phcdn.net and 24% (4 requests) were made to Secure.phabricator.com. The less responsive or slowest element that took the longest time to load (638 ms) relates to the external source P.phcdn.net.
Page size can be reduced by 94.3 kB (91%)
103.5 kB
9.2 kB
In fact, the total size of Phabricator.com main page is 103.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 103.5 kB which makes up the majority of the site volume.
Potential reduce by 94.3 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 94.3 kB or 91% of the original size.
Number of requests can be reduced by 5 (42%)
12
7
The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phabricator. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for CSS and as a result speed up the page load time.
phabricator.com
157 ms
secure.phabricator.com
487 ms
core.pkg.css
301 ms
font-lato.css
315 ms
phui-fontkit.css
319 ms
font-aleo.css
444 ms
phui-theme.css
549 ms
init.js
327 ms
core.pkg.js
533 ms
PHUIXIconView.js
528 ms
266 ms
605 ms
608 ms
lato-regular.woff
24 ms
lato-bold.woff
38 ms
fontawesome-webfont.woff
638 ms
maniphest.pkg.css
10 ms
phabricator.com 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
phabricator.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
phabricator.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phabricator.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Phabricator.com 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.
phabricator.com
Open Graph description is not detected on the main page of Phabricator. 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: