Tools & Wizards About Us
writingforresults.net screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

writingforresults.net

Briefing Notes & Briefing Books - Guidance, Templates & Training

Page Load Speed

4.5 sec in total

First Response

354 ms

Resources Loaded

1.3 sec

Page Rendered

2.9 sec

writingforresults.net screenshot

About Website

Click here to check amazing Writingforresults content for Canada. Otherwise, check out these important facts you probably never knew about writingforresults.net

Henry Ford said, ‘Nothing is particularly hard if you divide it into small jobs.’ Writing for Results does just that for briefing notes and briefing books.

Visit writingforresults.net

Key Findings

We analyzed Writingforresults.net page load time and found that the first response time was 354 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

writingforresults.net performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

writingforresults.net

354 ms

mm_menu.js

170 ms

I.aspx

75 ms

in.js

29 ms

jsapi

30 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 49% of them (36 requests) were addressed to the original Writingforresults.net, 11% (8 requests) were made to Thefreedictionary.com and 9% (7 requests) were made to Img.tfd.com. The less responsive or slowest element that took the longest time to load (804 ms) belongs to the original domain Writingforresults.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 305.6 kB (31%)

Content Size

976.0 kB

After Optimization

670.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Writingforresults.net main page is 976.0 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. 40% of websites need less resources to load. Images take 806.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 108.8 kB

  • Original 131.9 kB
  • After minification 117.8 kB
  • After compression 23.1 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. This page needs HTML code to be minified as it can gain 14.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 108.8 kB or 82% of the original size.

Image Optimization

-23%

Potential reduce by 181.9 kB

  • Original 806.7 kB
  • After minification 624.8 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, Writingforresults needs image optimization as it can save up to 181.9 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-40%

Potential reduce by 14.9 kB

  • Original 37.4 kB
  • After minification 37.0 kB
  • After compression 22.5 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 14.9 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (46%)

Requests Now

65

After Optimization

35

  • AJAX
  • Images
  • JavaScript

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Writingforresults. 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 as a result speed up the page load time.

Network Requests Diagram

writingforresults.net

writingforresults.net

354 ms

mm_menu.js

mm_menu.js

170 ms

I.aspx

I.aspx

75 ms

in.js

in.js

29 ms

jsapi

jsapi

30 ms

default.css

default.css

74 ms

element.js

element.js

216 ms

loader.js

loader.js

287 ms

js1.aspx

js1.aspx

306 ms

js1.aspx

js1.aspx

251 ms

js1.aspx

js1.aspx

251 ms

js1.aspx

js1.aspx

306 ms

js1.aspx

js1.aspx

305 ms

js1.aspx

js1.aspx

305 ms

js1.aspx

js1.aspx

351 ms

counter.js

counter.js

169 ms

counter.js

counter.js

169 ms

urchin.js

urchin.js

134 ms

quant.js

quant.js

170 ms

get

get

70 ms

webValidator.aspx

webValidator.aspx

169 ms

I.aspx

I.aspx

243 ms

blue-seal-250-52-whitetxt-writingforresultsinc-49362.png

blue-seal-250-52-whitetxt-writingforresultsinc-49362.png

255 ms

Help.gif

Help.gif

220 ms

spacer.gif

spacer.gif

147 ms

index_r1_c1_s1.jpg

index_r1_c1_s1.jpg

147 ms

index_r2_c1_s1.jpg

index_r2_c1_s1.jpg

205 ms

index_r2_c2_s1.jpg

index_r2_c2_s1.jpg

224 ms

index_r2_c3_s1.jpg

index_r2_c3_s1.jpg

254 ms

index_r3_c2_s1.jpg

index_r3_c2_s1.jpg

223 ms

index_r4_c2_s1.jpg

index_r4_c2_s1.jpg

223 ms

index_r5_c2_s1.jpg

index_r5_c2_s1.jpg

221 ms

index_r6_c2_s1.jpg

index_r6_c2_s1.jpg

254 ms

index_r7_c2_s1.jpg

index_r7_c2_s1.jpg

263 ms

index_r8_c2_s1.jpg

index_r8_c2_s1.jpg

263 ms

index_r9_c2_s1.jpg

index_r9_c2_s1.jpg

264 ms

index_r10_c2_s1.jpg

index_r10_c2_s1.jpg

263 ms

index_r11_c2_s1.jpg

index_r11_c2_s1.jpg

362 ms

index_r12_c2.gif

index_r12_c2.gif

363 ms

index_r13_c2_s1.jpg

index_r13_c2_s1.jpg

363 ms

EAC_member_logo.jpg

EAC_member_logo.jpg

397 ms

Clarity.jpg

Clarity.jpg

363 ms

IABC.png

IABC.png

457 ms

PLAIN.png

PLAIN.png

469 ms

contents.fw.png

contents.fw.png

455 ms

signature.gif

signature.gif

395 ms

Writing-for-Results-Inc.png

Writing-for-Results-Inc.png

511 ms

Rob-8-1.jpg

Rob-8-1.jpg

804 ms

arrows.gif

arrows.gif

388 ms

mmmenu3_262x43_up.gif

mmmenu3_262x43_up.gif

434 ms

mmmenu4_219x43_up.gif

mmmenu4_219x43_up.gif

446 ms

mmmenu2_343x43_up.gif

mmmenu2_343x43_up.gif

463 ms

mmmenu1_240x43_up.gif

mmmenu1_240x43_up.gif

445 ms

like.php

like.php

119 ms

g-y-rss.gif

g-y-rss.gif

47 ms

Enrico_Caruso.jpeg

Enrico_Caruso.jpeg

77 ms

Black_Hawk_Down_Super64_over_Mogadishu_coast.jpg

Black_Hawk_Down_Super64_over_Mogadishu_coast.jpg

74 ms

Svaughan.jpg

Svaughan.jpg

69 ms

descartes.jpg

descartes.jpg

66 ms

hangman.aspx

hangman.aspx

104 ms

t.php

t.php

93 ms

__utm.gif

__utm.gif

11 ms

rules-p-a3xxlqtk05o-E.js

rules-p-a3xxlqtk05o-E.js

10 ms

rules-p-a3xxlqtk05o-E.js

rules-p-a3xxlqtk05o-E.js

63 ms

blxue7LW05k.js

blxue7LW05k.js

77 ms

FEppCFCt76d.png

FEppCFCt76d.png

78 ms

hangman.png

hangman.png

44 ms

pixel;r=2034918354;rf=0;a=p-a3xxlqtk05o-E;url=http%3A%2F%2Fwritingforresults.net%2F;uht=2;fpan=1;fpa=P0-2041431661-1664830637249;pbc=;ns=0;ce=1;qjs=1;qv=39016d63-20220929161725;cm=;gdpr=0;ref=;d=writingforresults.net;dst=0;et=1664830637249;tzo=-180;ogl=;ses=116f2546-db90-4aa2-a6c3-4343d60694af

pixel;r=2034918354;rf=0;a=p-a3xxlqtk05o-E;url=http%3A%2F%2Fwritingforresults.net%2F;uht=2;fpan=1;fpa=P0-2041431661-1664830637249;pbc=;ns=0;ce=1;qjs=1;qv=39016d63-20220929161725;cm=;gdpr=0;ref=;d=writingforresults.net;dst=0;et=1664830637249;tzo=-180;ogl=;ses=116f2546-db90-4aa2-a6c3-4343d60694af

54 ms

FollowCompany.js

FollowCompany.js

93 ms

index_r2_c2_s2.jpg

index_r2_c2_s2.jpg

72 ms

index_r4_c2_s2.jpg

index_r4_c2_s2.jpg

73 ms

index_r6_c2_s2.jpg

index_r6_c2_s2.jpg

72 ms

index_r8_c2_s2.jpg

index_r8_c2_s2.jpg

71 ms

index_r10_c2_s2.jpg

index_r10_c2_s2.jpg

69 ms

Accessibility Review

writingforresults.net accessibility score

63

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

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

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

writingforresults.net best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

writingforresults.net SEO score

54

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Writingforresults.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Writingforresults.net 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

writingforresults.net

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