Tools & Wizards About Us
wlink.com.np screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wlink.com.np

WorldLink Communications Ltd.

Page Load Speed

7.6 sec in total

First Response

870 ms

Resources Loaded

6 sec

Page Rendered

689 ms

wlink.com.np screenshot

About Website

Welcome to wlink.com.np homepage info - get ready to check W Link Com best content for Nepal right away, or after learning these important things about wlink.com.np

WorldLink Communications is an Internet service provider in Nepal. The nation's largest ISP, it has 700,000 active consumer accounts and 2,000 business accounts

Visit wlink.com.np

Key Findings

We analyzed Wlink.com.np page load time and found that the first response time was 870 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

wlink.com.np performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

wlink.com.np

870 ms

worldlink.com.np

1820 ms

349d9edd71591d0ff28ecb99f91a20c2.css

1250 ms

post-2541.css

742 ms

post-814.css

1243 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 Wlink.com.np, 77% (49 requests) were made to Worldlink.com.np and 14% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Worldlink.com.np.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (63%)

Content Size

2.3 MB

After Optimization

872.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wlink.com.np main page is 2.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. 70% of websites need less resources to load. Images take 713.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 503.8 kB

  • Original 576.1 kB
  • After minification 547.7 kB
  • After compression 72.3 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 503.8 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 32.3 kB

  • Original 713.1 kB
  • After minification 680.9 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. W Link Com images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 248.5 kB

  • Original 350.7 kB
  • After minification 350.7 kB
  • After compression 102.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 248.5 kB or 71% of the original size.

CSS Optimization

-98%

Potential reduce by 675.4 kB

  • Original 692.2 kB
  • After minification 181.0 kB
  • After compression 16.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. Wlink.com.np needs all CSS files to be minified and compressed as it can save up to 675.4 kB or 98% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (49%)

Requests Now

53

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wlink.com.np

wlink.com.np

870 ms

worldlink.com.np

worldlink.com.np

1820 ms

349d9edd71591d0ff28ecb99f91a20c2.css

349d9edd71591d0ff28ecb99f91a20c2.css

1250 ms

post-2541.css

post-2541.css

742 ms

post-814.css

post-814.css

1243 ms

post-35989.css

post-35989.css

784 ms

jquery.min.js

jquery.min.js

1495 ms

js

js

62 ms

css

css

35 ms

post-1274.css

post-1274.css

837 ms

post-1327.css

post-1327.css

988 ms

post-78094.css

post-78094.css

803 ms

post-36214.css

post-36214.css

1249 ms

post-1453.css

post-1453.css

1265 ms

post-1456.css

post-1456.css

1531 ms

slick.min.js

slick.min.js

1264 ms

hoverIntent.min.js

hoverIntent.min.js

1264 ms

maxmegamenu.js

maxmegamenu.js

1529 ms

widgets.js

widgets.js

1529 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1572 ms

webpack.runtime.min.js

webpack.runtime.min.js

1667 ms

frontend-modules.min.js

frontend-modules.min.js

1571 ms

frontend.min.js

frontend.min.js

1894 ms

waypoints.min.js

waypoints.min.js

1895 ms

frontend.min.js

frontend.min.js

2000 ms

elements-handlers.min.js

elements-handlers.min.js

1894 ms

lazyload.min.js

lazyload.min.js

1892 ms

gtm.js

gtm.js

171 ms

long-arrow-right.svg

long-arrow-right.svg

727 ms

search.svg

search.svg

847 ms

plans-circle-mobile.svg

plans-circle-mobile.svg

864 ms

circle.svg

circle.svg

869 ms

plans-circle.svg

plans-circle.svg

868 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

104 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf

181 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf

310 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf

309 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjQ.ttf

312 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf

312 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

312 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjQ.ttf

313 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjQ.ttf

313 ms

destination

destination

315 ms

fbevents.js

fbevents.js

310 ms

wlinkLogo-white.svg

wlinkLogo-white.svg

273 ms

go-direct-plans.png

go-direct-plans.png

323 ms

img-2-pzt2uahmnj7jhyqmpyaerufdruavc5hhna1nmyokqi.jpg

img-2-pzt2uahmnj7jhyqmpyaerufdruavc5hhna1nmyokqi.jpg

341 ms

speedtest-logo.svg

speedtest-logo.svg

363 ms

Google-logo.svg

Google-logo.svg

378 ms

Airtel_Africa_logo.svg

Airtel_Africa_logo.svg

377 ms

Nokia-logo.svg

Nokia-logo.svg

544 ms

Meraki-Logo.svg

Meraki-Logo.svg

570 ms

Social-Media-post-1024x1024.jpg

Social-Media-post-1024x1024.jpg

1090 ms

beacon.png

beacon.png

617 ms

Nettv-logo.png

Nettv-logo.png

639 ms

appp.jpg

appp.jpg

1170 ms

Google-Play-badge.svg

Google-Play-badge.svg

816 ms

App-Store-badge-1.svg

App-Store-badge-1.svg

819 ms

WhatsApp-Image-2022-12-29-at-11.46.15.jpeg

WhatsApp-Image-2022-12-29-at-11.46.15.jpeg

869 ms

qq-1024x602.jpg

qq-1024x602.jpg

957 ms

viber_image_2022-12-14_16-11-49-584-1024x682.jpg

viber_image_2022-12-14_16-11-49-584-1024x682.jpg

1358 ms

bhusan.jpg

bhusan.jpg

1309 ms

Google-Play-badge.svg

Google-Play-badge.svg

1121 ms

App-Store-badge.svg

App-Store-badge.svg

1222 ms

Accessibility Review

wlink.com.np accessibility score

81

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

wlink.com.np 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

SEO Factors

wlink.com.np SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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 Wlink.com.np 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 Wlink.com.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

wlink.com.np

Open Graph data is detected on the main page of W Link Com. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: