3.8 sec in total
697 ms
3 sec
110 ms
Visit pangea.ai now to see the best up-to-date Pangea content for India and also check out these interesting facts you probably never knew about pangea.ai
The Pangea.ai score enables transparency to decide between hundreds of software development firms. Get access — hire and scale talent with confidence.
Visit pangea.aiWe analyzed Pangea.ai page load time and found that the first response time was 697 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
pangea.ai performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value7.9 s
3/100
25%
Value12.3 s
3/100
10%
Value15,040 ms
0/100
30%
Value0.026
100/100
15%
Value24.5 s
0/100
10%
697 ms
76 ms
299 ms
697 ms
934 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 57% of them (25 requests) were addressed to the original Pangea.ai, 27% (12 requests) were made to Pangeacdn.azureedge.net and 7% (3 requests) were made to Stpangeacms.blob.core.windows.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Pangeacdn.azureedge.net.
Page size can be reduced by 70.0 kB (17%)
420.3 kB
350.2 kB
In fact, the total size of Pangea.ai main page is 420.3 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. 35% of websites need less resources to load. Images take 359.3 kB which makes up the majority of the site volume.
Potential reduce by 48.8 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 48.8 kB or 80% of the original size.
Potential reduce by 21.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. Pangea images are well optimized though.
Number of requests can be reduced by 19 (50%)
38
19
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pangea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
pangea.ai
697 ms
gtm.js
76 ms
3ad551e2fb3df521.css
299 ms
0cd2ce7baa193ee0.css
697 ms
9f026a8801aac7eb.css
934 ms
polyfills-c67a75d1b6f99dc8.js
1011 ms
webpack-a93f1ff900580176.js
750 ms
framework-ce84985cd166733a.js
1040 ms
main-fc1469642f2e0fa6.js
775 ms
_app-5a9647937799888c.js
1252 ms
ebaf4c27-d87c5853fd4e5df0.js
1251 ms
6835-d3d2cae6d38a20cf.js
1344 ms
8366-2089597017815e0c.js
1304 ms
5885-0c5e8687607bb785.js
1428 ms
5818-a44bd4fdf4cffa67.js
1379 ms
2913-4152a9b07251bad4.js
1648 ms
175-70457d7042e880f4.js
1699 ms
3839-5bdacb78a79b114c.js
1638 ms
index-9747164378d0c750.js
1715 ms
_buildManifest.js
1762 ms
_ssgManifest.js
1778 ms
small_Pangea_logo_a9b236a35b.webp
52 ms
hands_On_Laptop_6d83befcbd_e625eb8508.png
416 ms
astrounaut_07bd036cc9_5a28f29285.png
416 ms
hands_9699a4babf_6f4501db58.png
416 ms
large_Hero_image_new_2x_3c29717b5b.webp
613 ms
large_Hero_mobile_3x_3b5ef9bb15.webp
1917 ms
output_onlinepngtools_7_5339a39adc.png
541 ms
bolt_0fe290baf6_9c3281e905.png
483 ms
layer1_ec0f446c23_8b37fb4b0f.png
504 ms
Mask_group_5_8f5d764332_40f482cf33.png
593 ms
Blue_Navy_0b12e95a78_af14e40a13.png
861 ms
Group_943_c95ce30d57_0d11792409.png
874 ms
Vector_2_fe67b6368b_6c491b4a9f.png
1057 ms
Mask_group_6_ecb98b5673_795bea1ef4.png
967 ms
medium_Group_12651_ad027fe30d.webp
1142 ms
js
72 ms
hotjar-1807587.js
112 ms
modules.a4fd7e5489291affcf56.js
39 ms
poppins-v20-latin-regular.cc7a20fd.woff
1058 ms
poppins-v20-latin-500.c470b7dc.woff
1066 ms
poppins-v20-latin-600.bcc8b08c.woff
1078 ms
futura-bt-medium.16dd6f9f.woff
1107 ms
futura-bt-book.32c032b0.woff
1110 ms
pangea.ai 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.
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
ARIA IDs are not unique
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
pangea.ai 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
pangea.ai 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pangea.ai 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 Pangea.ai 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.
pangea.ai
Open Graph description is not detected on the main page of Pangea. 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: