Tools & Wizards About Us
thirtyflirty.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

thirtyflirty.com

Thirty Flirty Over 30s Dating

Page Load Speed

2.5 sec in total

First Response

536 ms

Resources Loaded

1.6 sec

Page Rendered

322 ms

thirtyflirty.com screenshot

About Website

Visit thirtyflirty.com now to see the best up-to-date Thirty Flirty content and also check out these interesting facts you probably never knew about thirtyflirty.com

Thirty Flirty Dating is the World's Biggest and Best Online Dating Site for Over 30s Dating in Britain.

Visit thirtyflirty.com

Key Findings

We analyzed Thirtyflirty.com page load time and found that the first response time was 536 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

thirtyflirty.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

thirtyflirty.com

536 ms

css

76 ms

normalize.min.css

82 ms

foundation.min.css

158 ms

owl.carousel.css

159 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 35% of them (24 requests) were addressed to the original Thirtyflirty.com, 29% (20 requests) were made to Galcdn.datingfactory.net and 6% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (536 ms) belongs to the original domain Thirtyflirty.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 290.6 kB (20%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thirtyflirty.com main page is 1.4 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 33.5 kB

  • Original 43.6 kB
  • After minification 39.9 kB
  • After compression 10.1 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 33.5 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 21.4 kB

  • 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. Thirty Flirty images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 220.9 kB

  • Original 325.8 kB
  • After minification 325.8 kB
  • After compression 104.8 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 220.9 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 14.7 kB

  • Original 18.2 kB
  • After minification 17.2 kB
  • After compression 3.5 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. Thirtyflirty.com needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

64

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thirtyflirty.com

thirtyflirty.com

536 ms

css

css

76 ms

normalize.min.css

normalize.min.css

82 ms

foundation.min.css

foundation.min.css

158 ms

owl.carousel.css

owl.carousel.css

159 ms

index.common.css

index.common.css

173 ms

index.css

index.css

163 ms

df.js

df.js

318 ms

theme.js

theme.js

170 ms

Index.js

Index.js

231 ms

modernizr.min.js

modernizr.min.js

232 ms

fastclick.min.js

fastclick.min.js

243 ms

owl.carousel.min.js

owl.carousel.min.js

250 ms

adsbygoogle.js

adsbygoogle.js

31 ms

2612f35c5f2a459d520aa00c50752346.png

2612f35c5f2a459d520aa00c50752346.png

45 ms

9bb31b89883dbdf7811c3f2a0dd0961c.png

9bb31b89883dbdf7811c3f2a0dd0961c.png

58 ms

f86223f0daad1d93060e4426ed1a9dbb.png

f86223f0daad1d93060e4426ed1a9dbb.png

52 ms

33b53bbe0ec9a109f370c668b6271a54.png

33b53bbe0ec9a109f370c668b6271a54.png

43 ms

f82084c07862d2f4a84a339f1e60ff41.png

f82084c07862d2f4a84a339f1e60ff41.png

394 ms

d0cd0a15aa3c68301c41f47b991b9097.png

d0cd0a15aa3c68301c41f47b991b9097.png

42 ms

80394e883b3db339a37aa8cdb943e955.png

80394e883b3db339a37aa8cdb943e955.png

68 ms

49810c4db005728cc6dc3f6ff2439b39.png

49810c4db005728cc6dc3f6ff2439b39.png

73 ms

bb94553fe09432730ae92bf8c35da347.png

bb94553fe09432730ae92bf8c35da347.png

73 ms

5b418ac7dea0cc877ced128c9c378740.png

5b418ac7dea0cc877ced128c9c378740.png

74 ms

3e41b4d1eb13915cec7faa8ee83b9e9d.png

3e41b4d1eb13915cec7faa8ee83b9e9d.png

82 ms

e3a0dce32bfd33cab45735c2a1c4a0d8.png

e3a0dce32bfd33cab45735c2a1c4a0d8.png

441 ms

0413c6f7d45660b5e970f2e6f3cc7050.png

0413c6f7d45660b5e970f2e6f3cc7050.png

87 ms

68cdf0d57c33194c15fc785c7ead978a.png

68cdf0d57c33194c15fc785c7ead978a.png

85 ms

fcfcba7a9e2dabde51129768bc08fcd6.png

fcfcba7a9e2dabde51129768bc08fcd6.png

88 ms

aa6c9970c586b4837c2e54ae34970ca0.png

aa6c9970c586b4837c2e54ae34970ca0.png

97 ms

c054d242022294c5541420bee7b8831d.png

c054d242022294c5541420bee7b8831d.png

98 ms

397a2250a7398a34f87e3f38f0fe5d51.png

397a2250a7398a34f87e3f38f0fe5d51.png

98 ms

d454bf04ad6e5f1c23302822c3651365.png

d454bf04ad6e5f1c23302822c3651365.png

99 ms

f1b15dbb6ed96ccd8ae6649d97a728a8.png

f1b15dbb6ed96ccd8ae6649d97a728a8.png

109 ms

visual.jpg

visual.jpg

377 ms

logo.png

logo.png

84 ms

icon-twitter.png

icon-twitter.png

85 ms

icon-fb.png

icon-fb.png

90 ms

SwitchLocale.js

SwitchLocale.js

79 ms

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

45 ms

mRDHwJdvwTinms3TRtD3HQLUuEpTyoUstqEm5AMlJo4.ttf

mRDHwJdvwTinms3TRtD3HQLUuEpTyoUstqEm5AMlJo4.ttf

55 ms

courgette-regular-webfont.woff

courgette-regular-webfont.woff

178 ms

selector_arrow_bottom.gif

selector_arrow_bottom.gif

81 ms

RegistrationShort.js

RegistrationShort.js

81 ms

select-arrow.png

select-arrow.png

97 ms

ico_warning.gif

ico_warning.gif

96 ms

widgets.js

widgets.js

95 ms

sdk.js

sdk.js

155 ms

ca-pub-5761316233310933.js

ca-pub-5761316233310933.js

73 ms

zrt_lookup.html

zrt_lookup.html

108 ms

show_ads_impl.js

show_ads_impl.js

108 ms

ga.js

ga.js

17 ms

__utm.gif

__utm.gif

44 ms

__utm.gif

__utm.gif

79 ms

icon_auth.png

icon_auth.png

103 ms

providers.gif

providers.gif

103 ms

ajs.php

ajs.php

192 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

144 ms

ads

ads

320 ms

collect

collect

82 ms

osd.js

osd.js

21 ms

133 ms

xd_arbiter.php

xd_arbiter.php

68 ms

xd_arbiter.php

xd_arbiter.php

142 ms

syndication

syndication

98 ms

690326142608371713

690326142608371713

152 ms

lg.php

lg.php

90 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

42 ms

Accessibility Review

thirtyflirty.com accessibility score

72

Accessibility Issues

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

thirtyflirty.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

thirtyflirty.com SEO score

87

Search Engine Optimization Advices

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 Thirtyflirty.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 Thirtyflirty.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

thirtyflirty.com

Open Graph description is not detected on the main page of Thirty Flirty. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: