Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

wp.stories.google

Web Stories for WordPress - Download the free WordPress plugin

Page Load Speed

742 ms in total

First Response

54 ms

Resources Loaded

297 ms

Page Rendered

391 ms

wp.stories.google screenshot

About Website

Welcome to wp.stories.google homepage info - get ready to check Wp Stories best content for India right away, or after learning these important things about wp.stories.google

With Web Stories for WordPress, we're bringing first-class Web Stories support to WordPress. Make visual stories on the web your very own, and immerse your readers in great and fast-loading full-s...

Visit wp.stories.google

Key Findings

We analyzed Wp.stories.google page load time and found that the first response time was 54 ms and then it took 688 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

wp.stories.google performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

wp.stories.google

54 ms

v0.js

40 ms

amp-analytics-0.1.js

56 ms

amp-animation-0.1.js

61 ms

amp-bind-0.1.js

68 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 50% of them (6 requests) were addressed to the original Wp.stories.google, 50% (6 requests) were made to Cdn.ampproject.org. The less responsive or slowest element that took the longest time to load (142 ms) belongs to the original domain Wp.stories.google.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.3 kB (8%)

Content Size

367.8 kB

After Optimization

337.4 kB

In fact, the total size of Wp.stories.google main page is 367.8 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. 20% of websites need less resources to load. Javascripts take 185.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 29.9 kB

  • Original 39.1 kB
  • After minification 39.1 kB
  • After compression 9.2 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 29.9 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 142.9 kB
  • After minification 142.9 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. Wp Stories images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 461 B

  • Original 185.8 kB
  • After minification 185.8 kB
  • After compression 185.4 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.

Requests Breakdown

Number of requests can be reduced by 5 (45%)

Requests Now

11

After Optimization

6

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

Accessibility Review

wp.stories.google accessibility score

87

Accessibility Issues

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

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

Image elements do not have [alt] attributes

Best Practices

wp.stories.google 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

High

Page has valid source maps

SEO Factors

wp.stories.google SEO score

93

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

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 Wp.stories.google 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 Wp.stories.google 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 PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: