Tools & Wizards About Us
wri.tt screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wri.tt

Write! App - Minimalist Text Editor for Distraction-Free Writing

Page Load Speed

5.6 sec in total

First Response

191 ms

Resources Loaded

3.7 sec

Page Rendered

1.7 sec

wri.tt screenshot

About Website

Welcome to wri.tt homepage info - get ready to check Wri best content for United States right away, or after learning these important things about wri.tt

Write! app is a perfect text editor that helps you focus on what matters and turn your ideas into meaningful stories. Support for cloud allows you to have all this in one place.

Visit wri.tt

Key Findings

We analyzed Wri.tt page load time and found that the first response time was 191 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster. This domain responded with an error, which can significantly jeopardize Wri.tt rating and web reputation

Performance Metrics

wri.tt performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value5.7 s

50/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

wri.tt

191 ms

wri.tt

410 ms

style.css

190 ms

mac.css

282 ms

font-awesome.min.css

25 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 69% of them (61 requests) were addressed to the original Wri.tt, 4% (4 requests) were made to D.adroll.com and 3% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Wri.tt.

Page Optimization Overview & Recommendations

Page size can be reduced by 575.4 kB (23%)

Content Size

2.5 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wri.tt main page is 2.5 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. 40% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.0 kB

  • Original 42.0 kB
  • After minification 38.1 kB
  • After compression 9.0 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 33.0 kB or 79% of the original size.

Image Optimization

-15%

Potential reduce by 307.2 kB

  • Original 2.1 MB
  • After minification 1.8 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. Obviously, Wri needs image optimization as it can save up to 307.2 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-55%

Potential reduce by 121.8 kB

  • Original 221.9 kB
  • After minification 209.0 kB
  • After compression 100.1 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 121.8 kB or 55% of the original size.

CSS Optimization

-84%

Potential reduce by 113.4 kB

  • Original 135.3 kB
  • After minification 119.0 kB
  • After compression 22.0 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. Wri.tt needs all CSS files to be minified and compressed as it can save up to 113.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (32%)

Requests Now

79

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wri.tt

wri.tt

191 ms

wri.tt

wri.tt

410 ms

style.css

style.css

190 ms

mac.css

mac.css

282 ms

font-awesome.min.css

font-awesome.min.css

25 ms

css

css

58 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

561 ms

script.js

script.js

372 ms

analytics.js

analytics.js

103 ms

bg_pattern.png

bg_pattern.png

116 ms

header-logo.png

header-logo.png

114 ms

header-logo-hover.png

header-logo-hover.png

114 ms

big-logo.png

big-logo.png

186 ms

feather_with_shadow.png

feather_with_shadow.png

281 ms

laptop.png

laptop.png

738 ms

bottom_shadow_new.png

bottom_shadow_new.png

186 ms

screen_light.png

screen_light.png

461 ms

screen_dark.png

screen_dark.png

369 ms

logo-registration.png

logo-registration.png

368 ms

money_back_guarantee_badge.png

money_back_guarantee_badge.png

372 ms

small_animated_circle.png

small_animated_circle.png

359 ms

logotypes_mac-pc.png

logotypes_mac-pc.png

452 ms

checkmark.png

checkmark.png

454 ms

popup_bottom.png

popup_bottom.png

457 ms

question_mark_default.png

question_mark_default.png

464 ms

question_mark_active.png

question_mark_active.png

543 ms

quote_left.png

quote_left.png

544 ms

quote_right.png

quote_right.png

546 ms

logo_footer.png

logo_footer.png

549 ms

bottom_layer2.png

bottom_layer2.png

560 ms

bottom_layer3.png

bottom_layer3.png

636 ms

feather_footer.png

feather_footer.png

636 ms

0064.js

0064.js

171 ms

wide-shadow3.png

wide-shadow3.png

692 ms

bg_gradient.png

bg_gradient.png

598 ms

radial-bg.png

radial-bg.png

1178 ms

splitter.png

splitter.png

685 ms

new_control.png

new_control.png

683 ms

new_control_hover.png

new_control_hover.png

691 ms

first_part.png

first_part.png

864 ms

second-part.png

second-part.png

963 ms

third_part.png

third_part.png

960 ms

fourth_part.png

fourth_part.png

788 ms

registration-panel.png

registration-panel.png

784 ms

registration-panel-pixel.png

registration-panel-pixel.png

876 ms

registration-panel-bottom.png

registration-panel-bottom.png

881 ms

collect

collect

33 ms

email_active.png

email_active.png

906 ms

fb_default.png

fb_default.png

920 ms

gplus_default.png

gplus_default.png

924 ms

collect

collect

56 ms

twitter_default.png

twitter_default.png

925 ms

linkedin_default.png

linkedin_default.png

924 ms

ga-audiences

ga-audiences

44 ms

email.gif

email.gif

836 ms

pass.gif

pass.gif

754 ms

pcworld.png

pcworld.png

757 ms

pcworld_hover.png

pcworld_hover.png

825 ms

lifehacker.png

lifehacker.png

824 ms

lifehacker_hover.png

lifehacker_hover.png

743 ms

tnw_hover.png

tnw_hover.png

752 ms

makeuseof.png

makeuseof.png

754 ms

makeuseof_hover.png

makeuseof_hover.png

824 ms

lifehack.png

lifehack.png

820 ms

icon_mail.png

icon_mail.png

743 ms

icon_fb.png

icon_fb.png

752 ms

icon_twitter.png

icon_twitter.png

755 ms

icon_google.png

icon_google.png

768 ms

UT4A4azGdo8ivJbCxlvqUw.js

UT4A4azGdo8ivJbCxlvqUw.js

138 ms

t.js

t.js

60 ms

roundtrip.js

roundtrip.js

27 ms

JCI4PJLR7ZBVFH6M4FUYIN.js

JCI4PJLR7ZBVFH6M4FUYIN.js

94 ms

track.js

track.js

243 ms

s

s

7 ms

out

out

20 ms

tr

tr

179 ms

tr

tr

189 ms

out

out

9 ms

out

out

27 ms

u.php

u.php

198 ms

sync

sync

138 ms

adsct

adsct

159 ms

pixel

pixel

98 ms

47 ms

sd

sd

4 ms

377928.gif

377928.gif

9 ms

pixel

pixel

15 ms

in

in

4 ms

tap.php

tap.php

291 ms

Accessibility Review

wri.tt accessibility score

88

Accessibility Issues

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

Image elements do not have [alt] attributes

Best Practices

wri.tt 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

High

Page has valid source maps

SEO Factors

wri.tt SEO score

93

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

wri.tt

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