Tools & Wizards About Us
katrina.in screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

katrina.in

Personalized Emails and URLs

Page Load Speed

737 ms in total

First Response

17 ms

Resources Loaded

423 ms

Page Rendered

297 ms

katrina.in screenshot

About Website

Click here to check amazing Katrina content. Otherwise, check out these important facts you probably never knew about katrina.in

We provide Personalized Emails and URLs on premium website names for a fraction of the amount it cost to own such names.

Visit katrina.in

Key Findings

We analyzed Katrina.in page load time and found that the first response time was 17 ms and then it took 720 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

katrina.in performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

katrina.in

17 ms

email

59 ms

v0.js

70 ms

amp-consent-0.1.js

70 ms

amp-analytics-0.1.js

71 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 10% of them (1 request) were addressed to the original Katrina.in, 30% (3 requests) were made to Cdn.ampproject.org and 20% (2 requests) were made to Jupiterin.swipepages.media. The less responsive or slowest element that took the longest time to load (219 ms) relates to the external source Jupiterin.swipepages.media.

Page Optimization Overview & Recommendations

Page size can be reduced by 367 B (0%)

Content Size

143.6 kB

After Optimization

143.3 kB

  • HTML
  • JavaScript

In fact, the total size of Katrina.in main page is 143.6 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. 25% of websites need less resources to load. Javascripts take 143.2 kB which makes up the majority of the site volume.

HTML Optimization

-38%

Potential reduce by 148 B

  • Original 391 B
  • After minification 368 B
  • After compression 243 B

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 148 B or 38% of the original size.

JavaScript Optimization

-0%

Potential reduce by 219 B

  • Original 143.2 kB
  • After minification 143.2 kB
  • After compression 143.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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Katrina. According to our analytics all requests are already optimized.

Network Requests Diagram

katrina.in

katrina.in

17 ms

email

email

59 ms

v0.js

v0.js

70 ms

amp-consent-0.1.js

amp-consent-0.1.js

70 ms

amp-analytics-0.1.js

amp-analytics-0.1.js

71 ms

css

css

49 ms

pattern-four.svg

pattern-four.svg

139 ms

patterns-2.svg

patterns-2.svg

219 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

31 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

36 ms

Accessibility Review

katrina.in accessibility score

33

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

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

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 [lang] attribute

Best Practices

katrina.in 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

High

Page has valid source maps

SEO Factors

katrina.in SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Katrina.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Katrina.in 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

katrina.in

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