Tools & Wizards About Us
iamnepal.co screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

iamnepal.co

NepalVue - Nepal's Favourite Source of Information

Page Load Speed

16.2 sec in total

First Response

180 ms

Resources Loaded

8.2 sec

Page Rendered

7.8 sec

iamnepal.co screenshot

About Website

Welcome to iamnepal.co homepage info - get ready to check Iam Nepal best content right away, or after learning these important things about iamnepal.co

Everything you need to know about Nepal. Stories from the Himalayan Nation. Nepal's Favourite Source of Information

Visit iamnepal.co

Key Findings

We analyzed Iamnepal.co page load time and found that the first response time was 180 ms and then it took 16 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

iamnepal.co performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.4 s

0/100

25%

SI (Speed Index)

Value27.8 s

0/100

10%

TBT (Total Blocking Time)

Value25,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value40.4 s

0/100

10%

Network Requests Diagram

iamnepal.co

180 ms

nepalvue.com

1857 ms

wp-emoji-release.min.js

391 ms

canvas.css

167 ms

powerkit.css

394 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Iamnepal.co, 88% (87 requests) were made to Nepalvue.com and 3% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Nepalvue.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 344.5 kB (56%)

Content Size

612.5 kB

After Optimization

267.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iamnepal.co main page is 612.5 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. 70% of websites need less resources to load. HTML takes 314.1 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 278.3 kB

  • Original 314.1 kB
  • After minification 304.0 kB
  • After compression 35.7 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 278.3 kB or 89% of the original size.

Image Optimization

-30%

Potential reduce by 1.1 kB

  • Original 3.8 kB
  • After minification 2.6 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. Obviously, Iam Nepal needs image optimization as it can save up to 1.1 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 18.1 kB

  • Original 123.1 kB
  • After minification 123.1 kB
  • After compression 105.0 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 18.1 kB or 15% of the original size.

CSS Optimization

-27%

Potential reduce by 46.9 kB

  • Original 171.5 kB
  • After minification 171.4 kB
  • After compression 124.6 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. Iamnepal.co needs all CSS files to be minified and compressed as it can save up to 46.9 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 88 (94%)

Requests Now

94

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iam Nepal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 50 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

iamnepal.co

iamnepal.co

180 ms

nepalvue.com

nepalvue.com

1857 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

391 ms

canvas.css

canvas.css

167 ms

powerkit.css

powerkit.css

394 ms

style.min.css

style.min.css

512 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

496 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

520 ms

block.css

block.css

555 ms

block.css

block.css

666 ms

block.css

block.css

657 ms

block.css

block.css

752 ms

block.css

block.css

772 ms

block-row.css

block-row.css

775 ms

block-justified-gallery.css

block-justified-gallery.css

819 ms

block-slider-gallery.css

block-slider-gallery.css

956 ms

block-posts-sidebar.css

block-posts-sidebar.css

676 ms

absolute-reviews-public.css

absolute-reviews-public.css

688 ms

advanced-popups-public.css

advanced-popups-public.css

702 ms

block.css

block.css

1077 ms

block.css

block.css

758 ms

block.css

block.css

992 ms

block.css

block.css

973 ms

block.css

block.css

974 ms

block.css

block.css

1033 ms

cookie-law-info-public.css

cookie-law-info-public.css

926 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

940 ms

public-powerkit-author-box.css

public-powerkit-author-box.css

1244 ms

public-powerkit-basic-elements.css

public-powerkit-basic-elements.css

1211 ms

public-powerkit-coming-soon.css

public-powerkit-coming-soon.css

1235 ms

public-powerkit-content-formatting.css

public-powerkit-content-formatting.css

1232 ms

public-powerkit-contributors.css

public-powerkit-contributors.css

1282 ms

public-powerkit-facebook.css

public-powerkit-facebook.css

1331 ms

public-powerkit-featured-categories.css

public-powerkit-featured-categories.css

1457 ms

public-powerkit-inline-posts.css

public-powerkit-inline-posts.css

1480 ms

public-powerkit-instagram.css

public-powerkit-instagram.css

1473 ms

public-powerkit-justified-gallery.css

public-powerkit-justified-gallery.css

1263 ms

adsbygoogle.js

adsbygoogle.js

387 ms

js

js

424 ms

js

js

468 ms

adsbygoogle.js

adsbygoogle.js

460 ms

pinit.js

pinit.js

404 ms

e-202242.js

e-202242.js

344 ms

public-powerkit-lazyload.css

public-powerkit-lazyload.css

1454 ms

glightbox.min.css

glightbox.min.css

1422 ms

public-powerkit-lightbox.css

public-powerkit-lightbox.css

1254 ms

public-powerkit-opt-in-forms.css

public-powerkit-opt-in-forms.css

1368 ms

public-powerkit-pinterest.css

public-powerkit-pinterest.css

1274 ms

public-powerkit-scroll-to-top.css

public-powerkit-scroll-to-top.css

1242 ms

public-powerkit-share-buttons.css

public-powerkit-share-buttons.css

1364 ms

public-powerkit-slider-gallery.css

public-powerkit-slider-gallery.css

1294 ms

public-powerkit-social-links.css

public-powerkit-social-links.css

1278 ms

public-powerkit-table-of-contents.css

public-powerkit-table-of-contents.css

1102 ms

public-powerkit-twitter.css

public-powerkit-twitter.css

1402 ms

public-powerkit-widget-about.css

public-powerkit-widget-about.css

1391 ms

style.css

style.css

1297 ms

style.css

style.css

1351 ms

jetpack.css

jetpack.css

1583 ms

cookie-law-info-table.css

cookie-law-info-table.css

1467 ms

jquery.min.js

jquery.min.js

1306 ms

jquery-migrate.min.js

jquery-migrate.min.js

1427 ms

advanced-popups-public.js

advanced-popups-public.js

1292 ms

cookie-law-info-public.js

cookie-law-info-public.js

1119 ms

cookie-law-info-ccpa.js

cookie-law-info-ccpa.js

1302 ms

photon.min.js

photon.min.js

3112 ms

public-block-alert.js

public-block-alert.js

1319 ms

public-block-collapsibles.js

public-block-collapsibles.js

3096 ms

public-block-tabs.js

public-block-tabs.js

1267 ms

jquery.justifiedGallery.min.js

jquery.justifiedGallery.min.js

3076 ms

public-block-justified-gallery.js

public-block-justified-gallery.js

2906 ms

imagesloaded.min.js

imagesloaded.min.js

2884 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

2885 ms

public-block-slider-gallery.js

public-block-slider-gallery.js

2839 ms

index.js

index.js

2856 ms

index.js

index.js

2839 ms

public-powerkit-basic-elements.js

public-powerkit-basic-elements.js

2790 ms

public-powerkit-justified-gallery.js

public-powerkit-justified-gallery.js

2664 ms

lazysizes.config.js

lazysizes.config.js

2668 ms

lazysizes.min.js

lazysizes.min.js

3226 ms

glightbox.min.js

glightbox.min.js

3169 ms

public-powerkit-lightbox.js

public-powerkit-lightbox.js

3154 ms

public-powerkit-opt-in-forms.js

public-powerkit-opt-in-forms.js

3103 ms

public-powerkit-pin-it.js

public-powerkit-pin-it.js

3002 ms

public-powerkit-scroll-to-top.js

public-powerkit-scroll-to-top.js

2997 ms

public-powerkit-share-buttons.js

public-powerkit-share-buttons.js

3120 ms

public-powerkit-slider-gallery.js

public-powerkit-slider-gallery.js

3010 ms

public-powerkit-table-of-contents.js

public-powerkit-table-of-contents.js

2933 ms

scripts.js

scripts.js

3002 ms

script.min.js

script.min.js

2950 ms

zrt_lookup.html

zrt_lookup.html

1910 ms

26cc9e3ef2ddc3612c448be4df90229b

26cc9e3ef2ddc3612c448be4df90229b

1814 ms

nepalvue-logo-dark.png

nepalvue-logo-dark.png

1609 ms

nepalvue-logo-light.png

nepalvue-logo-light.png

1613 ms

show_ads_impl.js

show_ads_impl.js

1232 ms

powerkit-icons.woff

powerkit-icons.woff

688 ms

analytics.js

analytics.js

316 ms

powerkit-icons.woff

powerkit-icons.woff

698 ms

icons.ttf

icons.ttf

694 ms

sdk.js

sdk.js

684 ms

Accessibility Review

iamnepal.co accessibility score

92

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

button, link, and menuitem elements do not have accessible names.

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

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

Links do not have a discernible name

Best Practices

iamnepal.co best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

iamnepal.co SEO score

93

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iamnepal.co 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 Iamnepal.co 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

iamnepal.co

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: