Tools & Wizards About Us
writeforresults.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

writeforresults.com

Win more bids | Write like 'The Economist': Write for Results

Page Load Speed

7.9 sec in total

First Response

986 ms

Resources Loaded

6.5 sec

Page Rendered

407 ms

writeforresults.com screenshot

About Website

Visit writeforresults.com now to see the best up-to-date Write For Results content and also check out these interesting facts you probably never knew about writeforresults.com

Write for Results transform the business writing skills of top professionals and organisations across the world. Contact us to find out more.

Visit writeforresults.com

Key Findings

We analyzed Writeforresults.com page load time and found that the first response time was 986 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

writeforresults.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.181

67/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

writeforresults.com

986 ms

js

68 ms

style.min.css

320 ms

font-awesome-legacy.min.css

241 ms

grid-system.css

248 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 63% of them (69 requests) were addressed to the original Writeforresults.com, 15% (16 requests) were made to Static.libsyn.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Writeforresults.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 205.8 kB (2%)

Content Size

13.2 MB

After Optimization

13.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Writeforresults.com main page is 13.2 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. 65% of websites need less resources to load. Images take 12.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 115.5 kB

  • Original 142.3 kB
  • After minification 139.1 kB
  • After compression 26.8 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 115.5 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 87.4 kB

  • Original 12.7 MB
  • After minification 12.6 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. Write For Results images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.6 kB

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

CSS Optimization

-1%

Potential reduce by 1.2 kB

  • Original 120.8 kB
  • After minification 120.8 kB
  • After compression 119.6 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. Writeforresults.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 62 (66%)

Requests Now

94

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

writeforresults.com

writeforresults.com

986 ms

js

js

68 ms

style.min.css

style.min.css

320 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

241 ms

grid-system.css

grid-system.css

248 ms

style.css

style.css

332 ms

header-secondary-nav.css

header-secondary-nav.css

264 ms

element-testimonial.css

element-testimonial.css

322 ms

element-clients.css

element-clients.css

326 ms

caroufredsel.css

caroufredsel.css

352 ms

css

css

34 ms

responsive.css

responsive.css

399 ms

skin-original.css

skin-original.css

401 ms

menu-dynamic.css

menu-dynamic.css

405 ms

widget-nectar-posts.css

widget-nectar-posts.css

410 ms

js_composer.min.css

js_composer.min.css

440 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

460 ms

css

css

36 ms

jquery.min.js

jquery.min.js

463 ms

jquery-migrate.min.js

jquery-migrate.min.js

382 ms

frontend-gtag.min.js

frontend-gtag.min.js

388 ms

style-non-critical.css

style-non-critical.css

129 ms

jquery.fancybox.css

jquery.fancybox.css

167 ms

core.css

core.css

183 ms

core.min.js

core.min.js

233 ms

menu.min.js

menu.min.js

233 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

234 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

365 ms

wp-polyfill.min.js

wp-polyfill.min.js

364 ms

dom-ready.min.js

dom-ready.min.js

365 ms

hooks.min.js

hooks.min.js

364 ms

i18n.min.js

i18n.min.js

363 ms

a11y.min.js

a11y.min.js

363 ms

autocomplete.min.js

autocomplete.min.js

549 ms

wpss-search-suggest.js

wpss-search-suggest.js

550 ms

jquery.easing.min.js

jquery.easing.min.js

550 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

547 ms

priority.js

priority.js

546 ms

transit.min.js

transit.min.js

550 ms

waypoints.js

waypoints.js

638 ms

imagesLoaded.min.js

imagesLoaded.min.js

639 ms

hoverintent.min.js

hoverintent.min.js

639 ms

jquery.fancybox.js

jquery.fancybox.js

638 ms

touchswipe.min.js

touchswipe.min.js

638 ms

caroufredsel.min.js

caroufredsel.min.js

636 ms

nectar-testimonial-slider.js

nectar-testimonial-slider.js

741 ms

anime.min.js

anime.min.js

735 ms

superfish.js

superfish.js

730 ms

init.js

init.js

795 ms

comment-reply.min.js

comment-reply.min.js

713 ms

js_composer_front.min.js

js_composer_front.min.js

709 ms

forms.js

forms.js

795 ms

analytics.js

analytics.js

31 ms

scott-logo-without-strapline-colour.jpg

scott-logo-without-strapline-colour.jpg

715 ms

stamp-03.jpg

stamp-03.jpg

718 ms

Icon-stamp-02.jpg

Icon-stamp-02.jpg

710 ms

stamp-01.jpg

stamp-01.jpg

709 ms

MBP_0534.jpg

MBP_0534.jpg

1330 ms

MBP_0537.jpg

MBP_0537.jpg

3230 ms

Allen-Overy-Client.jpg

Allen-Overy-Client.jpg

790 ms

196263562

196263562

334 ms

informa-client.jpg

informa-client.jpg

769 ms

PWC-Client.jpg

PWC-Client.jpg

776 ms

BAE-Systems-client.jpg

BAE-Systems-client.jpg

782 ms

The-Economist-client.jpg

The-Economist-client.jpg

848 ms

238 ms

collect

collect

139 ms

DMW.jpg

DMW.jpg

718 ms

Sheffield-Health-Social-Care-Charity.jpg

Sheffield-Health-Social-Care-Charity.jpg

731 ms

EY1.jpg

EY1.jpg

741 ms

linklaters.jpg

linklaters.jpg

801 ms

slaughter-and-may.jpg

slaughter-and-may.jpg

800 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

187 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

188 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

244 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

276 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

277 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

277 ms

icomoon.woff

icomoon.woff

815 ms

js

js

138 ms

libsyn-fonts.css

libsyn-fonts.css

211 ms

bootstrap.min.css

bootstrap.min.css

198 ms

custom-player-bootstrap.min.css

custom-player-bootstrap.min.css

212 ms

font-awesome.min.css

font-awesome.min.css

217 ms

css

css

103 ms

jcarousel.responsive.css

jcarousel.responsive.css

215 ms

jquery.min.js

jquery.min.js

208 ms

bootstrap.min.js

bootstrap.min.js

244 ms

moment.min.js

moment.min.js

212 ms

player-0.0.12.min.js

player-0.0.12.min.js

250 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

240 ms

608689159-83c4530178669ea4f58e223272ddd8f3cb8a94278e910f9f3fbc07468d471e75-d

608689159-83c4530178669ea4f58e223272ddd8f3cb8a94278e910f9f3fbc07468d471e75-d

523 ms

website.png

website.png

236 ms

rss.png

rss.png

236 ms

lock-black.svg

lock-black.svg

235 ms

rss-sm.png

rss-sm.png

233 ms

download.png

download.png

232 ms

embed.png

embed.png

237 ms

share.png

share.png

238 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

850 ms

Gensler_logo-223x47-86bdd223.gif

Gensler_logo-223x47-86bdd223.gif

697 ms

Jane_Podcast_Oct_2017.png

Jane_Podcast_Oct_2017.png

54 ms

libsyn-player-custom.png

libsyn-player-custom.png

56 ms

open-sans-v15-latin-regular.woff

open-sans-v15-latin-regular.woff

70 ms

open-sans-v15-latin-300.woff

open-sans-v15-latin-300.woff

41 ms

open-sans-v15-latin-600.woff

open-sans-v15-latin-600.woff

30 ms

open-sans-v15-latin-700.woff

open-sans-v15-latin-700.woff

41 ms

open-sans-v15-latin-800.woff

open-sans-v15-latin-800.woff

40 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

170 ms

Accessibility Review

writeforresults.com accessibility score

79

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

writeforresults.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

writeforresults.com SEO score

93

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

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 Writeforresults.com 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 Writeforresults.com 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

writeforresults.com

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