Tools & Wizards About Us
contenta.io screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

contenta.io

Smart Mobile Apps for Content Marketers & Bloggers - Contenta.io

Page Load Speed

4.1 sec in total

First Response

335 ms

Resources Loaded

3 sec

Page Rendered

759 ms

contenta.io screenshot

About Website

Welcome to contenta.io homepage info - get ready to check Contenta best content right away, or after learning these important things about contenta.io

Custom mobile apps for Content Marketers and Bloggers. Generate more leads and better engagement by sharing Wordpress on mobile, your Podcast and more.

Visit contenta.io

Key Findings

We analyzed Contenta.io page load time and found that the first response time was 335 ms and then it took 3.8 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

contenta.io performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value8,810 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.651

9/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

contenta.io

335 ms

contenta.io

460 ms

button.css

311 ms

css

50 ms

checkout.js

52 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 50% of them (19 requests) were addressed to the original Contenta.io, 16% (6 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Contenta.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.7 kB (12%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Contenta.io main page is 1.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. 45% of websites need less resources to load. Images take 840.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 139.9 kB

  • Original 170.2 kB
  • After minification 170.0 kB
  • After compression 30.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 139.9 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 48 B

  • Original 840.4 kB
  • After minification 840.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. Contenta images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.0 kB

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

CSS Optimization

-3%

Potential reduce by 1.8 kB

  • Original 64.5 kB
  • After minification 64.5 kB
  • After compression 62.7 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. Contenta.io has all CSS files already compressed.

Requests Breakdown

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

Requests Now

29

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

contenta.io

contenta.io

335 ms

contenta.io

contenta.io

460 ms

button.css

button.css

311 ms

css

css

50 ms

checkout.js

checkout.js

52 ms

autoptimize_bb3b2bfe371577df01bbb5c40c872368.js

autoptimize_bb3b2bfe371577df01bbb5c40c872368.js

590 ms

oct.js

oct.js

19 ms

analytics.js

analytics.js

159 ms

bg_ots_white-2.png

bg_ots_white-2.png

761 ms

supported_platforms-e1495680520355.png

supported_platforms-e1495680520355.png

497 ms

mobile-popups.png

mobile-popups.png

668 ms

email-marketing-services.png

email-marketing-services.png

543 ms

new-content-push-notification-contenta.png

new-content-push-notification-contenta.png

512 ms

content-notification-contenta.png

content-notification-contenta.png

674 ms

AdrewHScreenShot-1.png

AdrewHScreenShot-1.png

986 ms

ios-9-search-results-e1465925979605.png

ios-9-search-results-e1465925979605.png

940 ms

smartbanner-branch-e1460558576418.png

smartbanner-branch-e1460558576418.png

966 ms

Google-Analytics-icon-e1500251826319.png

Google-Analytics-icon-e1500251826319.png

1088 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

102 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

110 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

133 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

138 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexg.woff

139 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1133 ms

autoptimize_de9ef55116441566fa993bdb4da006e9.css

autoptimize_de9ef55116441566fa993bdb4da006e9.css

1171 ms

collect

collect

39 ms

collect

collect

9 ms

collect

collect

189 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1085 ms

fbevents.js

fbevents.js

104 ms

ga-audiences

ga-audiences

80 ms

adsct

adsct

122 ms

adsct

adsct

108 ms

260668150933094

260668150933094

156 ms

background_graph.jpg

background_graph.jpg

399 ms

bg_ots_bottom.jpg

bg_ots_bottom.jpg

556 ms

overlay.png

overlay.png

97 ms

z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuXMQQ.woff

z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuXMQQ.woff

19 ms

Accessibility Review

contenta.io accessibility score

77

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

contenta.io best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

contenta.io 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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contenta.io 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 Contenta.io 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

contenta.io

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