6.3 sec in total
392 ms
4.8 sec
1.1 sec
Click here to check amazing VVM content for India. Otherwise, check out these important facts you probably never knew about vvm.org.in
VVM is a national program for popularizing science among school students of standards 6 to 11. VVM is supported by VIBHA, Vigyan Prasar, and NCERT.
Visit vvm.org.inWe analyzed Vvm.org.in page load time and found that the first response time was 392 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
vvm.org.in performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value33.8 s
0/100
25%
Value14.2 s
1/100
10%
Value2,360 ms
5/100
30%
Value0.001
100/100
15%
Value24.8 s
0/100
10%
392 ms
1169 ms
83 ms
552 ms
26 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 37% of them (50 requests) were addressed to the original Vvm.org.in, 16% (22 requests) were made to Static.cdninstagram.com and 11% (15 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Vvm.org.in.
Page size can be reduced by 1.4 MB (20%)
7.3 MB
5.8 MB
In fact, the total size of Vvm.org.in main page is 7.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.8 MB which makes up the majority of the site volume.
Potential reduce by 78.4 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 33.2 kB, which is 35% 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 78.4 kB or 83% of the original size.
Potential reduce by 1.1 MB
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. Obviously, VVM needs image optimization as it can save up to 1.1 MB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 168.2 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 168.2 kB or 79% of the original size.
Potential reduce by 132.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. Vvm.org.in needs all CSS files to be minified and compressed as it can save up to 132.8 kB or 80% of the original size.
Number of requests can be reduced by 74 (61%)
121
47
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VVM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
vvm.org.in
392 ms
vvm.org.in
1169 ms
js
83 ms
animate.css
552 ms
bootstrap.min.css
26 ms
all.css
40 ms
solid.css
52 ms
fontawesome.css
71 ms
style.css
926 ms
responsive.css
563 ms
magnific-popup.css
564 ms
owl.carousel.min.css
562 ms
jquery.slim.min.js
37 ms
popper.min.js
44 ms
bootstrap.bundle.min.js
45 ms
bootstrap.min.js
44 ms
particles.min.js
45 ms
stats.min.js
63 ms
script.js
386 ms
slick-theme.css
4 ms
slick.css
3 ms
slick.min.js
5 ms
popper.min.js
556 ms
bootstrap.min.js
612 ms
jquery.appear.min.js
564 ms
jquery.jCounter.js
565 ms
jquery.magnific-popup.min.js
755 ms
owl.carousel.min.js
740 ms
wow.min.js
754 ms
isotope.pkgd.min.js
1141 ms
css2
38 ms
css2
57 ms
css2
62 ms
counter.php
214 ms
genralsetting-1683965372uip7aHlGE27101cec6c38563ce056dc76c86a0336CZroFWG8l.png
214 ms
vvm-himalayas.png
214 ms
Shiksha1.png
213 ms
1.png
213 ms
2.png
474 ms
6.png
473 ms
3.png
473 ms
vvm_logo_2020-21.png
473 ms
5.png
491 ms
4.png
734 ms
icon1.png
734 ms
icon3.png
734 ms
icon2.png
734 ms
1683724544UD4pBe3bzd234adceddad55c012f37a9de2e1f97elR7wIgExA.jpg
857 ms
16837210257zgDQR9pkfc2741f9c2c727ef38ed0ba54dc7aaa3PY2oIyKjv.jpg
961 ms
1683721008BcnJp537I263f2ea8ad1fee41f09fd7e2064a4d46ztk2EOANj.jpg
1199 ms
1683720992MclU52HXVce5fe44e4ae6aa9ff8f9d7698c79acd8r6jtbCMRQ.jpg
1015 ms
1683720976EnyuXezI4fa0a23967a65369fdb707ffc52261396y3NCgTM2R.jpg
1020 ms
16826764921yR7xY9Fc846b986f8aeaff16a8d0432efffba1b1JfLQADSaO.jpg
1208 ms
1682668359fZps4zHan5e793b6037c730cf7ebe21fb6f18f8a4CFzvVMUrx.jpg
1207 ms
1682668300eFyVJEawXffc9de39c21ee788bb93d61796345a28t95RVBbz1.jpg
1222 ms
1684142742JMWhqZ47V896fe481606f732456c56e5bb997b7eeayrBXKkpi.jpg
1206 ms
youtube-logo.png
1418 ms
16841436003FhwjtPge9871b9df51bc7a82ff1f8a922a183c3bAJKsPB5VU.jpg
1386 ms
1684142948SdHyFqXrw8b479aeeba15d4c8dae7b6b91ba88568DpwtBqYEg.jpg
1392 ms
1684142089m7rPtGq6e5a393dbef604dbd06e6a5e847da20191Ea4ivSpOX.jpg
1577 ms
1684142074qi7PU32cW5320b44267a7ba7801acffe89a703a044Tw8taBp7.jpg
1400 ms
Group1.png
1417 ms
telegram.png
1758 ms
g5.png
1577 ms
VVM2020
408 ms
page.php
206 ms
434 ms
board.png
2088 ms
Rectangle23.png
2281 ms
bg-contactf.png
1929 ms
style.css
1883 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
152 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
209 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
208 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
209 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o18E.ttf
97 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o18E.ttf
96 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv18E.ttf
97 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv18E.ttf
115 ms
counter.php
342 ms
YSVNzQMiK3c.css
85 ms
Y7Y-iHUxgoM.js
93 ms
o1ndYS2og_B.js
92 ms
4Dr55_uVn75.js
135 ms
GGJYiuJ569H.js
139 ms
Glud--w-qOK.js
132 ms
_eawcKGGOQC.js
133 ms
p55HfXW__mM.js
133 ms
ALTQi95mOyD.js
142 ms
454436283_2136783303390268_3814510241754408424_n.jpg
57 ms
YnyA8SYgYgp.js
27 ms
299134043_1647803815621555_3415746193167235046_n.jpg
47 ms
UXtr_j2Fwe-.png
22 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
39 ms
runtime-b1c52fd0a13ead5fcf6b.js
80 ms
modules-96ebc7ac3ad66d681a3d.js
107 ms
main-babd9234dc048fb47339.js
115 ms
_app-a9c9f1a99e4414675fb1.js
146 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
141 ms
_buildManifest.js
164 ms
_ssgManifest.js
211 ms
0wSh4cMhbwx.css
60 ms
4KstZgooRhm.css
98 ms
X29_cDtL2_d.css
136 ms
Y7Y-iHUxgoM.js
159 ms
299335130_391341183130880_6015074582984993278_n.jpg
122 ms
p55HfXW__mM.js
106 ms
_pR8rlkT9uM.js
104 ms
7qw2AXH60hX.js
106 ms
LhSY3Ulh-8r.js
121 ms
-G7KoMA2lIG.js
122 ms
zmyrlirITdY.js
122 ms
MyYh9LiVF3b.js
123 ms
ruxamZrGq-3.js
123 ms
VtlkudaZd09.js
123 ms
NBY0lVmQTon.js
123 ms
NzRKGJeXERl.js
126 ms
ei4YGGztjBa.js
126 ms
Vvhlyc1XO8D.js
126 ms
c3Rnm_mCvjE.js
123 ms
cBfAkP0T1tP.js
125 ms
U6624O3JPyG.js
125 ms
ewM_TzK-3by.js
171 ms
274903457_216415034001493_3268710830530732956_n.jpg
176 ms
457200049_895389055952980_2070818101774553107_n.jpg
174 ms
456376513_893562579468961_8431741645182521686_n.jpg
179 ms
hwgTSgiJXcc.png
168 ms
8526.0c32a8f0cfc5749221a3.js
90 ms
1755.07a49c40b12af4f75780.js
94 ms
8283.f3e5048cca7cef5eed7f.js
56 ms
3077.44bfeb00af01bc4020f6.js
60 ms
1362.42d432e02f7980bca032.js
57 ms
4956.c4e51ef593974b9db0bb.js
60 ms
5893.d500bd2a89ded806aa73.js
56 ms
vvm.org.in 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-hidden="true"] elements contain focusable descendents
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
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
vvm.org.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
vvm.org.in 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 Vvm.org.in 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 Vvm.org.in 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.
vvm.org.in
Open Graph data is detected on the main page of VVM. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: