Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

pr3pr0d.emilydates.com

EmilyDates – A dating site for finding the perfect partner

Page Load Speed

2.7 sec in total

First Response

164 ms

Resources Loaded

1.8 sec

Page Rendered

700 ms

pr3pr0d.emilydates.com screenshot

About Website

Click here to check amazing Pr 3 0 D Emily Dates content for Nigeria. Otherwise, check out these important facts you probably never knew about pr3pr0d.emilydates.com

EmilyDates

Visit pr3pr0d.emilydates.com

Key Findings

We analyzed Pr3pr0d.emilydates.com page load time and found that the first response time was 164 ms and then it took 2.5 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

pr3pr0d.emilydates.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

en

164 ms

jquery.min.js

47 ms

sentry.101848f8809e4e22313d.js

438 ms

app.032a1c68696b4023fa73.js

665 ms

js

74 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 53% of them (20 requests) were addressed to the original Pr3pr0d.emilydates.com, 5% (2 requests) were made to Googletagmanager.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (665 ms) belongs to the original domain Pr3pr0d.emilydates.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 54.0 kB (18%)

Content Size

292.5 kB

After Optimization

238.5 kB

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

HTML Optimization

-72%

Potential reduce by 32.1 kB

  • Original 44.4 kB
  • After minification 39.4 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 5.0 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 32.1 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 131 B

  • Original 108.8 kB
  • After minification 108.7 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. Pr 3 0 D Emily Dates images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 21.7 kB

  • Original 51.9 kB
  • After minification 51.9 kB
  • After compression 30.3 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 21.7 kB or 42% of the original size.

CSS Optimization

-0%

Potential reduce by 74 B

  • Original 87.3 kB
  • After minification 87.3 kB
  • After compression 87.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. Pr3pr0d.emilydates.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (56%)

Requests Now

32

After Optimization

14

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

Accessibility Review

pr3pr0d.emilydates.com accessibility score

82

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

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

pr3pr0d.emilydates.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

Page has valid source maps

SEO Factors

pr3pr0d.emilydates.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 Pr3pr0d.emilydates.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 Pr3pr0d.emilydates.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 Pr 3 0 D Emily Dates. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: