Access pitchtoher.com.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

pitchtoher.com

713 ms

www.pitchtoher.com

1182 ms

layout.css

907 ms

abBlog.css

916 ms

home.css

632 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 71% of them (48 requests) were addressed to the original Pitchtoher.com, 4% (3 requests) were made to Staticxx.facebook.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Pitchtoher.com.

Content Size

1.6 MB

After Optimization

973.9 kB

In fact, the total size of Pitchtoher.com main page is 1.6 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. 60% of websites need less resources to load. Images take 782.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 30.6 kB

Original 39.5 kB
After minification 35.4 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. 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 30.6 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 20.7 kB

Original 782.9 kB
After minification 762.2 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. Pitchtoher images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 334.2 kB

Original 475.6 kB
After minification 419.9 kB
After compression 141.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 334.2 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 278.6 kB

Original 340.0 kB
After minification 326.3 kB
After compression 61.4 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. Pitchtoher.com needs all CSS files to be minified and compressed as it can save up to 278.6 kB or 82% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

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

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pitchtoher.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Pitchtoher.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

pitchtoher.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

pitchtoher.com

www.pitchtoher.com

layout.css

abBlog.css

home.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

pitchtoher.com

www.pitchtoher.com

layout.css

abBlog.css

home.css

font-awesome.min.css

jquery.flipster.css

jquery.min.js

cookie.js

jquery.flipster.js

socialShare.js

jquery.flexslider.js

top-pitches.css

owl.carousel.js

owl.carousel.css

all.js

widgets.js

2bfde5

analytics.js

fbevents.js

collect

collect

ga-audiences

mI_uheqN1Pc

bg-page.jpg

imgThumbpop.jpg

imgpoparrow.png

downImg.png

logo-lenovo.gif

logo-intel.png

bgPitchtoher.png

bg-tpInrCont2.png

imgWin1.jpg

imgWin2.jpg

imgWin3.jpg

thumb1.jpg

thumb2.jpg

thumb3.jpg

thumb4.jpg

imgYuwagirls.jpg

bgWinningteam.png

un-women.jpg

say-no-unite.jpg

half-the-sky.jpg