9.6 sec in total
480 ms
9 sec
88 ms
Visit git.prizm.digital now to see the best up-to-date Git Prizm content for Hong Kong and also check out these interesting facts you probably never knew about git.prizm.digital
Development Portal
Visit git.prizm.digitalWe analyzed Git.prizm.digital page load time and found that the first response time was 480 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
git.prizm.digital performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value1.5 s
100/100
25%
Value4.3 s
76/100
10%
Value600 ms
50/100
30%
Value0.346
32/100
15%
Value4.7 s
80/100
10%
480 ms
1016 ms
410 ms
674 ms
4607 ms
Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to Git.prizm.digital and no external sources were called. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Git.prizm.digital.
Page size can be reduced by 975.0 kB (71%)
1.4 MB
405.7 kB
In fact, the total size of Git.prizm.digital main page is 1.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. Only 10% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 24.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. 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 24.9 kB or 71% of the original size.
Potential reduce by 950.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 950.1 kB or 71% of the original size.
We found no issues to fix!
3
3
The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Git Prizm. According to our analytics all requests are already optimized.
git.prizm.digital
480 ms
git.prizm.digital
1016 ms
sign_in
410 ms
application-9880f992b4a3c109f2a12a3f4553d0fe.css
674 ms
application-cd4e557b2d6d44b68c2445862d96def8.js
4607 ms
SourceSansPro-Regular.ttf-62b8d062684da245eb4cd31ac6e0e3ad.woff
1122 ms
SourceSansPro-Light.ttf-e1fe6f1a6872032ae82b70da3084ec6f.woff
1318 ms
SourceSansPro-Semibold.ttf-f599cbfb81a904018c0ce5890f39595c.woff
1353 ms
SourceSansPro-Bold.ttf-5be8fe4ffce8ff2ddf7aa4cefdf763b5.woff
2086 ms
print-2cb1262fb60ceb73f2fe76fd1a61dccf.css
228 ms
git.prizm.digital accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s are not contained by their required parent element
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
Image elements do not have [alt] attributes
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.
git.prizm.digital best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
git.prizm.digital SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Git.prizm.digital 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 Git.prizm.digital 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.
git.prizm.digital
Open Graph data is detected on the main page of Git Prizm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: