Tools & Wizards About Us
psc.p1.gov.np screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

psc.p1.gov.np

गृहपृष्ठ | प्रदेश सरकार, प्रदेश लोक सेवा आयोग, , कोशी प्रदेश, विराटनगर

Page Load Speed

11.5 sec in total

First Response

1.1 sec

Resources Loaded

9.6 sec

Page Rendered

841 ms

psc.p1.gov.np screenshot

About Website

Visit psc.p1.gov.np now to see the best up-to-date Psc P 1 content for Nepal and also check out these interesting facts you probably never knew about psc.p1.gov.np

Visit psc.p1.gov.np

Key Findings

We analyzed Psc.p1.gov.np page load time and found that the first response time was 1.1 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

psc.p1.gov.np performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.7 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value1.289

1/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

psc.p1.gov.np

1080 ms

psc.koshi.gov.np

2657 ms

css

51 ms

style.css

1615 ms

bootstrap.css

1876 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Psc.p1.gov.np, 81% (52 requests) were made to Psc.koshi.gov.np and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Psc.koshi.gov.np.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (22%)

Content Size

4.7 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Psc.p1.gov.np main page is 4.7 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. 55% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 175.0 kB

  • Original 191.4 kB
  • After minification 110.3 kB
  • After compression 16.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 81.2 kB, which is 42% 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 175.0 kB or 91% of the original size.

Image Optimization

-3%

Potential reduce by 114.9 kB

  • Original 3.6 MB
  • After minification 3.5 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. Psc P 1 images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 226.6 kB

  • Original 318.1 kB
  • After minification 295.2 kB
  • After compression 91.5 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 226.6 kB or 71% of the original size.

CSS Optimization

-88%

Potential reduce by 490.8 kB

  • Original 559.7 kB
  • After minification 422.5 kB
  • After compression 68.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. Psc.p1.gov.np needs all CSS files to be minified and compressed as it can save up to 490.8 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (52%)

Requests Now

52

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Psc P 1. 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 from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

psc.p1.gov.np

psc.p1.gov.np

1080 ms

psc.koshi.gov.np

psc.koshi.gov.np

2657 ms

css

css

51 ms

style.css

style.css

1615 ms

bootstrap.css

bootstrap.css

1876 ms

magnific-popup.css

magnific-popup.css

818 ms

jquery-ui.css

jquery-ui.css

1102 ms

owl.carousel.min.css

owl.carousel.min.css

863 ms

owl.theme.default.min.css

owl.theme.default.min.css

1098 ms

animate.css

animate.css

1630 ms

all.min.css

all.min.css

1718 ms

flaticon.css

flaticon.css

1383 ms

aos.css

aos.css

1394 ms

style.css

style.css

1935 ms

style.main.css

style.main.css

1690 ms

sdk.js

sdk.js

19 ms

footertest.css

footertest.css

1885 ms

popup.main.css

popup.main.css

1902 ms

sdk.js

sdk.js

5 ms

30 ms

20221207121205.png

20221207121205.png

1822 ms

flag.gif

flag.gif

1823 ms

psclogo.png

psclogo.png

2416 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

1614 ms

jquery-migrate-3.0.1.min.js

jquery-migrate-3.0.1.min.js

1431 ms

jquery-ui.js

jquery-ui.js

2177 ms

popper.min.js

popper.min.js

1447 ms

bootstrap.min.js

bootstrap.min.js

1780 ms

jquery.marquee-1.3.1.min.js

jquery.marquee-1.3.1.min.js

1706 ms

owl.carousel.min.js

owl.carousel.min.js

1725 ms

jquery.stellar.min.js

jquery.stellar.min.js

1887 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

1981 ms

aos.js

aos.js

2005 ms

main.js

main.js

2075 ms

20240229182633.pdf

20240229182633.pdf

1949 ms

embed

embed

276 ms

20240131123946.jpg

20240131123946.jpg

4657 ms

20240131123928.jpg

20240131123928.jpg

4005 ms

20240131123740.jpg

20240131123740.jpg

1915 ms

20240131124317.jpg

20240131124317.jpg

1432 ms

20230203170443.jpeg

20230203170443.jpeg

3155 ms

20230203170909.jpg

20230203170909.jpg

2309 ms

20231204102004.png

20231204102004.png

2221 ms

20230117105657.jpg

20230117105657.jpg

2221 ms

20230117105922.jpg

20230117105922.jpg

2478 ms

202301191202180.jpg

202301191202180.jpg

2521 ms

202301191202181.jpg

202301191202181.jpg

2598 ms

202301191202182.jpg

202301191202182.jpg

2768 ms

202301191202183.jpg

202301191202183.jpg

2769 ms

202301191202184.jpg

202301191202184.jpg

3175 ms

202301191202185.jpg

202301191202185.jpg

3045 ms

20230117110353.jpg

20230117110353.jpg

3045 ms

20230518061407.jpg

20230518061407.jpg

3319 ms

20230117111453.jpg

20230117111453.jpg

3337 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf

105 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

157 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

204 ms

fa-solid-900.woff

fa-solid-900.woff

3719 ms

fa-regular-400.woff

fa-regular-400.woff

3504 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

221 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

270 ms

icomoon.ttf

icomoon.ttf

4379 ms

fa-brands-400.woff

fa-brands-400.woff

3580 ms

js

js

153 ms

Accessibility Review

psc.p1.gov.np accessibility score

58

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

psc.p1.gov.np best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

psc.p1.gov.np SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    NE

  • Language Claimed

    NP

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Psc.p1.gov.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 language. Our system also found out that Psc.p1.gov.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.

Social Sharing Optimization

psc.p1.gov.np

Open Graph description is not detected on the main page of Psc P 1. 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: