4.4 sec in total
103 ms
3.9 sec
454 ms
Visit pu.edu.np now to see the best up-to-date Pu content for Nepal and also check out these interesting facts you probably never knew about pu.edu.np
Visit pu.edu.npWe analyzed Pu.edu.np page load time and found that the first response time was 103 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pu.edu.np performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.9 s
14/100
25%
Value6.8 s
34/100
10%
Value1,370 ms
16/100
30%
Value0.058
98/100
15%
Value9.2 s
32/100
10%
103 ms
543 ms
155 ms
84 ms
82 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 35% of them (37 requests) were addressed to the original Pu.edu.np, 21% (22 requests) were made to Scontent.xx.fbcdn.net and 17% (18 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Legacy.nepalipatro.com.np.
Page size can be reduced by 429.6 kB (31%)
1.4 MB
944.9 kB
In fact, the total size of Pu.edu.np 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. 50% of websites need less resources to load. Images take 730.0 kB which makes up the majority of the site volume.
Potential reduce by 57.0 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 57.0 kB or 83% of the original size.
Potential reduce by 29.4 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. Pu images are well optimized though.
Potential reduce by 243.4 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 243.4 kB or 54% of the original size.
Potential reduce by 99.9 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. Pu.edu.np needs all CSS files to be minified and compressed as it can save up to 99.9 kB or 79% of the original size.
Number of requests can be reduced by 56 (58%)
97
41
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
pu.edu.np
103 ms
543 ms
style.css
155 ms
skeleton.css
84 ms
layout.css
82 ms
style-custom.php
259 ms
css
24 ms
default.min.css
80 ms
superfish.css
126 ms
prettyPhoto.css
169 ms
nivo-slider.css
122 ms
nivo-slider-style.css
122 ms
flexslider.css
172 ms
jquery.js
274 ms
jquery-migrate.min.js
170 ms
jquery.preloader.js
195 ms
recaptcha.css
202 ms
get
435 ms
element.js
51 ms
c.js
306 ms
superfish.js
142 ms
supersub.js
142 ms
hoverIntent.js
172 ms
gdl-scripts.js
178 ms
jquery.easing.js
185 ms
jquery.prettyPhoto.js
186 ms
jquery.nivo.slider.pack.js
290 ms
jquery.flexslider.js
292 ms
wp-emoji-release.min.js
198 ms
pattern-14.png
104 ms
ico.png
60 ms
head_back.png
202 ms
default-logo.png
58 ms
search-button-bg.png
50 ms
navigation-shadow.png
61 ms
loading.gif
62 ms
Central-Office-940x381.jpg
201 ms
Volume-On.png
93 ms
n80x15.gif
200 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
32 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
53 ms
ZCcPJiCGOzh84o2siPk48Z0EAVxt0G0biEntp43Qt6E.ttf
63 ms
cj2hUnSRBhwmSPr9kS589-LrC4Du4e_yfTJ8Ol60xk0.ttf
63 ms
c92rD_x0V1LslSFt3-QEpmsGzsqhEorxQDpu60nfWEc.ttf
90 ms
QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf
63 ms
likebox.php
360 ms
100003585355415
1417 ms
footer-bg.png
46 ms
translateelement.css
64 ms
main.js
74 ms
n80x15-7.gif
291 ms
t.js
292 ms
element_main.js
47 ms
xYm_UD1pmAz.css
291 ms
TGpOWuX6Pv8.css
358 ms
7kdskVxkCNz.css
436 ms
4bFiQ5zDJys.css
557 ms
_rx8naC75Dy.js
625 ms
x5F9OMjKyLw.js
650 ms
ICDbTSzjQEg.js
493 ms
TTCre3391I0.js
492 ms
njO1TPvGzoR.js
493 ms
b_6HNn_J2BZ.js
568 ms
7cm7D75Y0Sf.js
668 ms
rFmE1g6Dkoz.js
759 ms
ga.js
116 ms
loading.gif
66 ms
__utm.gif
12 ms
translate_24dp.png
55 ms
l
40 ms
googlelogo_color_42x16dp.png
54 ms
11054444_1448625752095761_6440649504694067882_n.jpg
356 ms
10857995_1400199600271710_3676599933506670154_n.jpg
441 ms
10850291_767575130002245_2333548365055000727_n.jpg
482 ms
12509210_1074102612640904_1022736012649705378_n.jpg
546 ms
12144843_979519872106982_779195146504740718_n.jpg
551 ms
1379841_10150004552801901_469209496895221757_n.jpg
553 ms
12745954_1700395146871460_8670648486239607007_n.jpg
549 ms
10394106_895354460481959_7900831823428704381_n.jpg
551 ms
12687880_970719523010970_7908413672952035924_n.jpg
552 ms
12274605_548034058705452_8519364734321025370_n.jpg
611 ms
12742443_1757733491126536_6483269472176267896_n.jpg
615 ms
12301710_780269495451773_125830320490843232_n.jpg
617 ms
12717804_892202097544874_6256649200148321273_n.jpg
616 ms
12744155_1856913007868824_3609009291161403941_n.jpg
618 ms
12417959_450957521775839_315300906327995706_n.jpg
616 ms
12512441_1554366278188374_4034033299236521325_n.jpg
811 ms
12741881_1553817161576619_2089091926719554460_n.jpg
815 ms
1935890_1551885398436462_3173622291656805353_n.jpg
749 ms
12742667_1551885391769796_4748672102469230139_n.jpg
749 ms
12734157_1551885388436463_6978070182770451583_n.jpg
747 ms
12715766_1551605601797775_6342880561476540196_n.jpg
749 ms
12745722_1551561218468880_9180457999686070374_n.jpg
948 ms
wL6VQj7Ab77.png
70 ms
s7jcwEQH7Sx.png
68 ms
QDwYpIaRyfG.png
71 ms
a-ZN6WoEOje.png
71 ms
A.site-addon.css,q201307130540.pagespeed.cf.D4RWddBvMz.css
27 ms
A.button.css,q201307130540.pagespeed.cf.dGgFk8-Nai.css
18 ms
A.jquery.qtip.css,q201307130540.pagespeed.cf.prJfpIBHgE.css
28 ms
jquery.min.js.pagespeed.jm.BDde6AetKX.js
51 ms
jquery.qtip.js
40 ms
I6-MnjEovm5.js
69 ms
vlXaquuXMrr.js
141 ms
bg_direction_nav_custom2.png
48 ms
pu.edu.np 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
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
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
pu.edu.np 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
Page has valid source maps
pu.edu.np SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
NE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pu.edu.np can be misinterpreted by Google and other search engines. Our service has detected that Nepali is used on the page, and it does not match the claimed English language. Our system also found out that Pu.edu.np 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.
pu.edu.np
Open Graph description is not detected on the main page of Pu. 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: