Tools & Wizards About Us
forsite.nu screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

forsite.nu

Truer than North – WordPress performance & scaling specialists

Page Load Speed

3.1 sec in total

First Response

657 ms

Resources Loaded

2 sec

Page Rendered

445 ms

forsite.nu screenshot

About Website

Welcome to forsite.nu homepage info - get ready to check Forsite best content right away, or after learning these important things about forsite.nu

Truer than North, we specialize in creating fast & scalable WordPress sites. WooCommerce, publishing and community sites. We make them fast.

Visit forsite.nu

Key Findings

We analyzed Forsite.nu page load time and found that the first response time was 657 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

forsite.nu performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

51/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value2.9 s

94/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

forsite.media

657 ms

A.style.css,qver=3.2.5.pagespeed.cf.eJHwiU36JD.css

96 ms

css

62 ms

A.jetpack.css,qver=3.9.4.pagespeed.cf.0CxwbW7n0N.css

182 ms

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

324 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Forsite.nu, 28% (10 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (657 ms) relates to the external source Forsite.media.

Page Optimization Overview & Recommendations

Page size can be reduced by 319.6 kB (48%)

Content Size

666.5 kB

After Optimization

346.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forsite.nu main page is 666.5 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 245.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 86.9 kB

  • Original 113.3 kB
  • After minification 113.3 kB
  • After compression 26.4 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 86.9 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 45 B

  • Original 245.4 kB
  • After minification 245.3 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. Forsite images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 66.2 kB

  • Original 109.9 kB
  • After minification 107.8 kB
  • After compression 43.7 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 66.2 kB or 60% of the original size.

CSS Optimization

-84%

Potential reduce by 166.5 kB

  • Original 197.9 kB
  • After minification 197.6 kB
  • After compression 31.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. Forsite.nu needs all CSS files to be minified and compressed as it can save up to 166.5 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

24

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forsite. 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

forsite.media

forsite.media

657 ms

A.style.css,qver=3.2.5.pagespeed.cf.eJHwiU36JD.css

A.style.css,qver=3.2.5.pagespeed.cf.eJHwiU36JD.css

96 ms

css

css

62 ms

A.jetpack.css,qver=3.9.4.pagespeed.cf.0CxwbW7n0N.css

A.jetpack.css,qver=3.9.4.pagespeed.cf.0CxwbW7n0N.css

182 ms

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

324 ms

wp-includes,_js,_jquery,_jquery-migrate.min.js,qver==1.2.1+wp-content,_themes,_fsm,_theme,_js,_fortytwo.min.js,qver==3.2.5.pagespeed.jc.MExFpqOYaF.js

wp-includes,_js,_jquery,_jquery-migrate.min.js,qver==1.2.1+wp-content,_themes,_fsm,_theme,_js,_fortytwo.min.js,qver==3.2.5.pagespeed.jc.MExFpqOYaF.js

252 ms

devicepx-jetpack.js

devicepx-jetpack.js

29 ms

om.js,qver=1.1.8.pagespeed.jm.tVtpHGLxJf.js

om.js,qver=1.1.8.pagespeed.jm.tVtpHGLxJf.js

259 ms

wp-content,_themes,_fsm,_theme,_lib,_widgets,_ft-responsive-slider,_js,_jquery.flexslider-min.js,qver==0.10.0+wp-content,_themes,_fsm,_theme,_js,_bootstrap.min.js,qver==3.1.1+wp-includes,_js,_wp-embed.min.js,qver==4.4.2.pagespeed.jc.xFO2OXfXgk.js

wp-content,_themes,_fsm,_theme,_lib,_widgets,_ft-responsive-slider,_js,_jquery.flexslider-min.js,qver==0.10.0+wp-content,_themes,_fsm,_theme,_js,_bootstrap.min.js,qver==3.1.1+wp-includes,_js,_wp-embed.min.js,qver==4.4.2.pagespeed.jc.xFO2OXfXgk.js

417 ms

e-201611.js

e-201611.js

37 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

87 ms

analytics.js

analytics.js

21 ms

collect

collect

3 ms

collect

collect

56 ms

xlogo.png.pagespeed.ic.kIobUUKZdZ.png

xlogo.png.pagespeed.ic.kIobUUKZdZ.png

300 ms

xbg.jpg.pagespeed.ic.O19f7awyV1.jpg

xbg.jpg.pagespeed.ic.O19f7awyV1.jpg

558 ms

380x285x737590013.png.pagespeed.ic.Ckm0m0P5xs.jpg

380x285x737590013.png.pagespeed.ic.Ckm0m0P5xs.jpg

320 ms

380x285x1318145635.png.pagespeed.ic.me_vJJPO8C.jpg

380x285x1318145635.png.pagespeed.ic.me_vJJPO8C.jpg

91 ms

380x285x521588366.png.pagespeed.ic.76W7CdlYBn.jpg

380x285x521588366.png.pagespeed.ic.76W7CdlYBn.jpg

318 ms

96x96x830341518.jpg.pagespeed.ic.gkMP88Mo4j.jpg

96x96x830341518.jpg.pagespeed.ic.gkMP88Mo4j.jpg

298 ms

96x96x3469956526.png.pagespeed.ic.Eq_hZjwu9-.png

96x96x3469956526.png.pagespeed.ic.Eq_hZjwu9-.png

318 ms

357147409.png

357147409.png

323 ms

96x96x4282544157.png.pagespeed.ic.Nb4CQTf7jA.jpg

96x96x4282544157.png.pagespeed.ic.Nb4CQTf7jA.jpg

324 ms

96x96x1600258358.png.pagespeed.ic.7i0ouRfMur.png

96x96x1600258358.png.pagespeed.ic.7i0ouRfMur.png

403 ms

u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff

u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff

259 ms

DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff

DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff

258 ms

MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff

MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff

304 ms

k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff

k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff

303 ms

toadOcfmlt9b38dHJxOBGAE-U1AYRUXXE0Dth8uKIE0.woff

toadOcfmlt9b38dHJxOBGAE-U1AYRUXXE0Dth8uKIE0.woff

294 ms

toadOcfmlt9b38dHJxOBGAAD_zxmsR6vL1X3tnvCZYo.woff

toadOcfmlt9b38dHJxOBGAAD_zxmsR6vL1X3tnvCZYo.woff

293 ms

ODelI1aHBYDBqgeIAH2zlBBHWFfxJXS04xYOz0jw624.woff

ODelI1aHBYDBqgeIAH2zlBBHWFfxJXS04xYOz0jw624.woff

289 ms

fpTVHK8qsXbIeTHTrnQH6L7TcrrtjxQtUk4wnkGIFYE.woff

fpTVHK8qsXbIeTHTrnQH6L7TcrrtjxQtUk4wnkGIFYE.woff

288 ms

fpTVHK8qsXbIeTHTrnQH6DugCgqSmF8aQZaqvLxtKh4.woff

fpTVHK8qsXbIeTHTrnQH6DugCgqSmF8aQZaqvLxtKh4.woff

290 ms

M2Jd71oPJhLKp0zdtTvoM1xDqsnd7zNt-b9r25av6rY.woff

M2Jd71oPJhLKp0zdtTvoM1xDqsnd7zNt-b9r25av6rY.woff

289 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

472 ms

g.gif

g.gif

84 ms

Accessibility Review

forsite.nu accessibility score

100

Accessibility Issues

Best Practices

forsite.nu 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

forsite.nu SEO score

100

Search Engine Optimization Advices

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

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forsite.nu 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 Dutch language. Our system also found out that Forsite.nu 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

forsite.nu

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