Tools & Wizards About Us
includewp.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

includewp.com

Top Frameworks for WordPress Plugin & Theme Developers – IncludeWP

Page Load Speed

2.5 sec in total

First Response

56 ms

Resources Loaded

1.8 sec

Page Rendered

615 ms

includewp.com screenshot

About Website

Visit includewp.com now to see the best up-to-date IncludeWP content for Turkey and also check out these interesting facts you probably never knew about includewp.com

IncludeWP is a leaderboard of the top open-source frameworks for WordPress plugin & WordPress theme developers. Because code reusability is awesome.

Visit includewp.com

Key Findings

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

Performance Metrics

includewp.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value3.5 s

89/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

includewp.com

56 ms

includewp.com

213 ms

fbevents.js

60 ms

jquery-2.1.1.min.js

58 ms

font-awesome.min.css

91 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 56% of them (41 requests) were addressed to the original Includewp.com, 10% (7 requests) were made to Cdnjs.cloudflare.com and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (779 ms) relates to the external source Yvoschaap.com.

Page Optimization Overview & Recommendations

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

Content Size

2.5 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Includewp.com 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 86.5 kB

  • Original 95.4 kB
  • After minification 64.0 kB
  • After compression 8.9 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 31.4 kB, which is 33% 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 86.5 kB or 91% of the original size.

Image Optimization

-29%

Potential reduce by 678.0 kB

  • Original 2.3 MB
  • After minification 1.7 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, IncludeWP needs image optimization as it can save up to 678.0 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 67 B

  • Original 21.6 kB
  • After minification 21.6 kB
  • After compression 21.6 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 26 B

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

Requests Breakdown

Number of requests can be reduced by 13 (21%)

Requests Now

63

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

includewp.com

includewp.com

56 ms

includewp.com

includewp.com

213 ms

fbevents.js

fbevents.js

60 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

58 ms

font-awesome.min.css

font-awesome.min.css

91 ms

css

css

92 ms

materialize.min.css

materialize.min.css

91 ms

materialize.min.js

materialize.min.js

93 ms

style.css

style.css

189 ms

email-decode.min.js

email-decode.min.js

53 ms

buttons.js

buttons.js

85 ms

oct.js

oct.js

39 ms

analytics.js

analytics.js

40 ms

sage.png

sage.png

178 ms

underscores.png

underscores.png

61 ms

boilerplate.png

boilerplate.png

199 ms

timber.jpg

timber.jpg

199 ms

cmb2.png

cmb2.png

332 ms

tgmpa.png

tgmpa.png

199 ms

redux.png

redux.png

275 ms

acf.png

acf.png

201 ms

meta-box.png

meta-box.png

252 ms

kirki.png

kirki.png

249 ms

unyson.png

unyson.png

329 ms

herbert.png

herbert.png

248 ms

pods.png

pods.png

276 ms

hybrid-core.png

hybrid-core.png

276 ms

wordpress-plugin-template.png

wordpress-plugin-template.png

328 ms

odin.png

odin.png

328 ms

themosis.png

themosis.png

328 ms

titan.png

titan.png

329 ms

fieldmanager.png

fieldmanager.png

331 ms

codestar.png

codestar.png

356 ms

vafpress.png

vafpress.png

330 ms

butterbean.png

butterbean.png

638 ms

cherry.png

cherry.png

358 ms

_child.png

_child.png

357 ms

nebula.png

nebula.png

361 ms

options.jpg

options.jpg

359 ms

wpcustomize.png

wpcustomize.png

358 ms

freemius.png

freemius.png

359 ms

dustpress.png

dustpress.png

360 ms

piklist.png

piklist.png

364 ms

wp-customizer-utilities.png

wp-customizer-utilities.png

362 ms

boots.png

boots.png

362 ms

options-definitely.png

options-definitely.png

363 ms

toolset.png

toolset.png

364 ms

post-types-definitely.png

post-types-definitely.png

382 ms

collect

collect

148 ms

adsct

adsct

275 ms

adsct

adsct

305 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

144 ms

Roboto-Regular.woff

Roboto-Regular.woff

145 ms

Roboto-Medium.woff

Roboto-Medium.woff

192 ms

Roboto-Light.woff

Roboto-Light.woff

194 ms

Roboto-Thin.woff

Roboto-Thin.woff

192 ms

Roboto-Bold.woff

Roboto-Bold.woff

195 ms

freemius-freebo-bot-wappu.svg

freemius-freebo-bot-wappu.svg

327 ms

counter.html

counter.html

605 ms

widgets.js

widgets.js

143 ms

bkg-pattern.png

bkg-pattern.png

210 ms

S6uyw4BMUTPHjxAwWw.ttf

S6uyw4BMUTPHjxAwWw.ttf

120 ms

FwZY7-Qmy14u9lezJ-6J6Mw.ttf

FwZY7-Qmy14u9lezJ-6J6Mw.ttf

152 ms

buttons.html

buttons.html

38 ms

js

js

164 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

50 ms

settings

settings

121 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

5 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

20 ms

embeds

embeds

28 ms

proxy.php

proxy.php

779 ms

collect

collect

14 ms

js

js

50 ms

Accessibility Review

includewp.com accessibility score

59

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

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

includewp.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

includewp.com SEO score

90

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

High

Tap targets are not sized appropriately

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

includewp.com

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