Tools & Wizards About Us

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

writingforresults.net

Briefing Notes & Briefing Books - Guidance, Templates & Training

Page Load Speed

5.2 sec in total

First Response

527 ms

Resources Loaded

4.1 sec

Page Rendered

573 ms

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 527 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

writingforresults.net performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value22.1 s

0/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value79.8 s

0/100

10%

Network Requests Diagram

writingforresults.net

527 ms

www.writingforresults.net

913 ms

style.min.css

39 ms

style.min.css

22 ms

theme.min.css

28 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 79% of them (41 requests) were addressed to the original Writingforresults.net, 17% (9 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Writingforresults.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.8 kB (0%)

Content Size

46.6 MB

After Optimization

46.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 97.1 kB

  • Original 116.4 kB
  • After minification 113.4 kB
  • After compression 19.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 97.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 20 B

  • Original 46.4 MB
  • After minification 46.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. Writingforresults images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 113 B

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

CSS Optimization

-1%

Potential reduce by 522 B

  • Original 61.9 kB
  • After minification 61.9 kB
  • After compression 61.4 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. Writingforresults.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 29 (74%)

Requests Now

39

After Optimization

10

  • Images
  • JavaScript
  • CSS

The browser has sent 39 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 15 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

writingforresults.net accessibility score

96

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.

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

Links do not have a discernible name

Best Practices

writingforresults.net 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

writingforresults.net SEO score

91

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

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

    TH

  • 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 it does not match the claimed Thai language. 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

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