5.6 sec in total
502 ms
4.9 sec
208 ms
Click here to check amazing Pratham content for India. Otherwise, check out these important facts you probably never knew about pratham.com
Pratham
Visit pratham.comWe analyzed Pratham.com page load time and found that the first response time was 502 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
pratham.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value5.5 s
19/100
25%
Value14.7 s
1/100
10%
Value460 ms
62/100
30%
Value0.52
15/100
15%
Value22.1 s
1/100
10%
502 ms
1030 ms
480 ms
712 ms
960 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 65% of them (41 requests) were addressed to the original Pratham.com, 10% (6 requests) were made to Youtube.com and 6% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Pratham.com.
Page size can be reduced by 748.6 kB (34%)
2.2 MB
1.5 MB
In fact, the total size of Pratham.com main page is 2.2 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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 17.6 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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.6 kB or 72% of the original size.
Potential reduce by 123.5 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. Pratham images are well optimized though.
Potential reduce by 298.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 298.6 kB or 61% of the original size.
Potential reduce by 309.0 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. Pratham.com needs all CSS files to be minified and compressed as it can save up to 309.0 kB or 83% of the original size.
Number of requests can be reduced by 13 (24%)
55
42
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pratham. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
pratham.com
502 ms
www.pratham.com
1030 ms
bootstrap.min.css
480 ms
style.css
712 ms
jquery-3.2.1.min.js
960 ms
jquery-1.11.1.min.js
1004 ms
bootstrap.min.js
742 ms
jquery.validate.js
752 ms
jquery.jscrollpane.js
754 ms
jquery.mousewheel.js
947 ms
conversion.js
123 ms
analytics.js
106 ms
pratham_logo.png
316 ms
slider_1.jpg
1186 ms
slider_2.jpg
1253 ms
slider_3.jpg
1252 ms
slider_4.jpg
1223 ms
slider_5.jpg
965 ms
slider_6.jpg
1196 ms
slider_7.jpg
1686 ms
welcome.png
1421 ms
ndtv_logo.png
1434 ms
award.png
1467 ms
pratham_logo.png
1500 ms
riviera_apt.png
1502 ms
riviera_duplex.png
1657 ms
pratham_logo.png
1671 ms
pratham_logo.png
1712 ms
pratham_logo.png
1750 ms
pratham_logo.png
1752 ms
pratham_logo.png
1893 ms
pratham_logo.png
1909 ms
pratham_logo.png
1924 ms
pratham_logo.png
1956 ms
upvan.png
1999 ms
vatika.png
2001 ms
avenue.png
2129 ms
enclave.png
2147 ms
pratham.png
2163 ms
fb_logo.png
2199 ms
youtube_logo.png
2246 ms
credai.png
2251 ms
IzCr8vI-Ws4
166 ms
PnMty3gGBDM
356 ms
9oTyHh-7Ipg
369 ms
ga.js
35 ms
70 ms
glyphicons-halflings-regular.woff
2268 ms
collect
23 ms
__utm.gif
12 ms
collect
86 ms
70 ms
www-player-vflMqr8uC.css
14 ms
www-embed-player.js
13 ms
base.js
59 ms
ga-audiences
142 ms
id
80 ms
8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js
77 ms
ad_status.js
172 ms
logo_ringo-vflOpz8ZI.png
268 ms
YubHWiCUdycrt9r0pwxtCFMvWBBxMHmgtw0lFaZzSbY.js
94 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
238 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
238 ms
pratham.com 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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
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.
pratham.com 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
Browser errors were logged to the console
pratham.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pratham.com 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 Pratham.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.
pratham.com
Open Graph description is not detected on the main page of Pratham. 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: