Tools & Wizards About Us
romantic.li screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

romantic.li

San Francisco Branding Agency | Romantic Brand Bureau

Page Load Speed

4.2 sec in total

First Response

342 ms

Resources Loaded

3.2 sec

Page Rendered

640 ms

romantic.li screenshot

About Website

Visit romantic.li now to see the best up-to-date Romantic content and also check out these interesting facts you probably never knew about romantic.li

Our branding agency Romantic creates brave new adventures for business, brands, and ideas—engaging companies in brand strategy, brand story, brand identity, and brand experience.

Visit romantic.li

Key Findings

We analyzed Romantic.li page load time and found that the first response time was 342 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

romantic.li performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value16.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.4 s

0/100

25%

SI (Speed Index)

Value38.4 s

0/100

10%

TBT (Total Blocking Time)

Value16,600 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value36.8 s

0/100

10%

Network Requests Diagram

romantic.li

342 ms

analytics.js

100 ms

wp-emoji-release.min.js

148 ms

style.min.css

148 ms

styles.css

129 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 81% of them (34 requests) were addressed to the original Romantic.li, 7% (3 requests) were made to Fonts.googleapis.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (507 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 116.8 kB (26%)

Content Size

453.6 kB

After Optimization

336.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Romantic.li main page is 453.6 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. 80% 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. CSS take 171.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 105.7 kB

  • Original 124.2 kB
  • After minification 122.9 kB
  • After compression 18.5 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 105.7 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 5.5 kB

  • Original 108.5 kB
  • After minification 103.0 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. Romantic images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.1 kB

  • Original 49.8 kB
  • After minification 49.8 kB
  • After compression 48.7 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

-3%

Potential reduce by 4.5 kB

  • Original 171.1 kB
  • After minification 171.1 kB
  • After compression 166.6 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. Romantic.li has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 29 (81%)

Requests Now

36

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Romantic. 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 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

romantic.li

romantic.li

342 ms

analytics.js

analytics.js

100 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

148 ms

style.min.css

style.min.css

148 ms

styles.css

styles.css

129 ms

rs6.css

rs6.css

137 ms

main.min.css

main.min.css

129 ms

ionicons.min.css

ionicons.min.css

212 ms

css

css

313 ms

css

css

338 ms

pum-site-styles.css

pum-site-styles.css

216 ms

style.min.css

style.min.css

223 ms

responsive.min.css

responsive.min.css

164 ms

Defaults.css

Defaults.css

217 ms

ultimate.min.css

ultimate.min.css

165 ms

jquery.js

jquery.js

309 ms

rbtools.min.js

rbtools.min.js

307 ms

rs6.min.js

rs6.min.js

335 ms

core.min.js

core.min.js

293 ms

ultimate.min.js

ultimate.min.js

334 ms

ultimate_bg.min.js

ultimate_bg.min.js

310 ms

scripts.js

scripts.js

302 ms

api.js

api.js

507 ms

script.js

script.js

304 ms

jquery.appear.js

jquery.appear.js

309 ms

main.min.js

main.min.js

306 ms

us.core.min.js

us.core.min.js

332 ms

position.min.js

position.min.js

307 ms

pum-site-scripts.js

pum-site-scripts.js

330 ms

wp-embed.min.js

wp-embed.min.js

329 ms

collect

collect

114 ms

css

css

127 ms

romantic-logo-C04-square-512-a-KYX-60x60-1.png

romantic-logo-C04-square-512-a-KYX-60x60-1.png

80 ms

romantic-logo-C04-square-kwx.png

romantic-logo-C04-square-kwx.png

68 ms

Russell-Helmet03.jpg

Russell-Helmet03.jpg

69 ms

romantic-logo-C04a-80x80.png

romantic-logo-C04a-80x80.png

68 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RkBI96.ttf

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RkBI96.ttf

231 ms

fa-solid-900.woff

fa-solid-900.woff

228 ms

fa-regular-400.woff

fa-regular-400.woff

217 ms

fa-light-300.woff

fa-light-300.woff

218 ms

fa-brands-400.woff

fa-brands-400.woff

214 ms

recaptcha__en.js

recaptcha__en.js

258 ms

Accessibility Review

romantic.li accessibility score

87

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-hidden="true"] elements contain focusable descendents

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

Links do not have a discernible name

Best Practices

romantic.li best practices score

75

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

SEO Factors

romantic.li SEO score

93

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

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 Romantic.li 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 Romantic.li 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

romantic.li

Open Graph description is not detected on the main page of Romantic. 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: