Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

thulo.us

One moment, please...

Page Load Speed

9.5 sec in total

First Response

697 ms

Resources Loaded

8.4 sec

Page Rendered

433 ms

thulo.us screenshot

About Website

Visit thulo.us now to see the best up-to-date Thulo content for Nepal and also check out these interesting facts you probably never knew about thulo.us

Buy Nepal made products in the USA. Delivered from Nepal & USA and shipping to all over US. Shop for Nepal t shirts, bags, jackets, shoes, leather, clothing, lehenga, kurta and every for your everyday...

Visit thulo.us

Key Findings

We analyzed Thulo.us page load time and found that the first response time was 697 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

thulo.us performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value24.3 s

0/100

10%

TBT (Total Blocking Time)

Value3,030 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.165

71/100

15%

TTI (Time to Interactive)

Value31.4 s

0/100

10%

Network Requests Diagram

thulo.us

697 ms

us.thulo.com

1290 ms

wp-emoji-release.min.js

48 ms

dashicons.min.css

54 ms

buttons.min.css

46 ms

Our browser made a total of 144 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Thulo.us, 92% (133 requests) were made to Us.thulo.com and 4% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Fonts.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (44%)

Content Size

5.1 MB

After Optimization

2.9 MB

In fact, the total size of Thulo.us main page is 5.1 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 442.0 kB

  • Original 494.5 kB
  • After minification 448.9 kB
  • After compression 52.5 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 442.0 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 2.9 kB

  • Original 2.4 MB
  • After minification 2.4 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. Thulo images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 687.7 kB

  • Original 895.0 kB
  • After minification 669.6 kB
  • After compression 207.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 687.7 kB or 77% of the original size.

CSS Optimization

-85%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.1 MB
  • After compression 197.7 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. Thulo.us needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 95 (73%)

Requests Now

130

After Optimization

35

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

Accessibility Review

thulo.us accessibility score

77

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

Image elements do not have [alt] attributes

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

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

High

Heading elements are not in a sequentially-descending order

Best Practices

thulo.us best practices score

92

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

SEO Factors

thulo.us SEO score

84

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

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 Thulo.us 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 Thulo.us 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

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