Tools & Wizards About Us

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

andthenwetried.com

And Then We Tried | Giving it our all, most of the time.

Page Load Speed

6.4 sec in total

First Response

232 ms

Resources Loaded

3.1 sec

Page Rendered

3 sec

About Website

Welcome to andthenwetried.com homepage info - get ready to check And Then We Tried best content for United States right away, or after learning these important things about andthenwetried.com

Three ladies trying out things from home improvement and DIY to beauty, fashion, and travel. Things may not always (ever?) go as planned but, hey, at least we tried.

Visit andthenwetried.com

Key Findings

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

Performance Metrics

andthenwetried.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value32.2 s

0/100

10%

TBT (Total Blocking Time)

Value61,100 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.056

98/100

15%

TTI (Time to Interactive)

Value75.5 s

0/100

10%

Network Requests Diagram

andthenwetried.com

232 ms

wp-emoji-release.min.js

31 ms

sbi-styles.min.css

48 ms

style.min.css

123 ms

mediaelementplayer-legacy.min.css

133 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 62% of them (56 requests) were addressed to the original Andthenwetried.com, 11% (10 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.1 kB (4%)

Content Size

2.1 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Andthenwetried.com main page is 2.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. 85% 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 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 79.0 kB

  • Original 99.8 kB
  • After minification 99.8 kB
  • After compression 20.8 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 79.0 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 2.9 kB

  • Original 1.8 MB
  • After minification 1.8 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. And Then We Tried images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

  • Original 81.1 kB
  • After minification 80.6 kB
  • After compression 80.0 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

-7%

Potential reduce by 8.1 kB

  • Original 119.4 kB
  • After minification 117.5 kB
  • After compression 111.3 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. Andthenwetried.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 50 (66%)

Requests Now

76

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

andthenwetried.com accessibility score

68

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 IDs are not unique

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Best Practices

andthenwetried.com best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

andthenwetried.com SEO score

70

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

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

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

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