Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

storiesbyemma.co

Home - Stories By Us - Web Copy + Content Marketing

Page Load Speed

2.9 sec in total

First Response

46 ms

Resources Loaded

1.9 sec

Page Rendered

987 ms

storiesbyemma.co screenshot

About Website

Welcome to storiesbyemma.co homepage info - get ready to check Stories Byemma best content right away, or after learning these important things about storiesbyemma.co

Want to improve your marketing? Stories By Us creates web copy, longform content, and case studies for growing companies.

Visit storiesbyemma.co

Key Findings

We analyzed Storiesbyemma.co page load time and found that the first response time was 46 ms and then it took 2.9 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

storiesbyemma.co performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value5.4 s

55/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

storiesbyemma.co

46 ms

storiesby.us

258 ms

jquery.js

84 ms

jquery-1.11.0.min.js

42 ms

jquery-migrate-1.2.1.min.js

43 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Storiesbyemma.co, 63% (31 requests) were made to Storiesby.us and 12% (6 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Storiesby.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.6 kB (6%)

Content Size

1.1 MB

After Optimization

1.0 MB

In fact, the total size of Storiesbyemma.co main page is 1.1 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. 70% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 63.4 kB

  • Original 79.1 kB
  • After minification 77.3 kB
  • After compression 15.7 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 63.4 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 232 B

  • Original 1.0 MB
  • After minification 1.0 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. Stories Byemma images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 12 (33%)

Requests Now

36

After Optimization

24

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stories Byemma. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

storiesbyemma.co accessibility score

63

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

storiesbyemma.co best practices score

75

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

High

Browser errors were logged to the console

SEO Factors

storiesbyemma.co SEO score

84

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

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Storiesbyemma.co 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 Storiesbyemma.co 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 Stories Byemma. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: