Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

solv.app

Solv: Find & Book Same-Day Urgent Care Near You

Page Load Speed

1.8 sec in total

First Response

334 ms

Resources Loaded

764 ms

Page Rendered

742 ms

solv.app screenshot

About Website

Visit solv.app now to see the best up-to-date Solv content and also check out these interesting facts you probably never knew about solv.app

Find and book same-day appointments for top-rated urgent cares, lab tests and telemed. Download the Solv app today! Convenient care, simplified with Solv.

Visit solv.app

Key Findings

We analyzed Solv.app page load time and found that the first response time was 334 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

solv.app performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value22.6 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value9,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value29.8 s

0/100

10%

Network Requests Diagram

www.solvhealth.com

334 ms

analytics.min.js

307 ms

solv_dark.svg

29 ms

location_triangle.svg

41 ms

in-person.svg

44 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Solv.app, 12% (4 requests) were made to Assets.solvhealth.com and 6% (2 requests) were made to Cdn.segment.com. The less responsive or slowest element that took the longest time to load (334 ms) relates to the external source Solvhealth.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.8 kB (34%)

Content Size

726.3 kB

After Optimization

476.5 kB

In fact, the total size of Solv.app main page is 726.3 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. 45% of websites need less resources to load. Images take 446.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 227.1 kB

  • Original 279.5 kB
  • After minification 279.2 kB
  • After compression 52.4 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 227.1 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 22.7 kB

  • Original 446.1 kB
  • After minification 423.4 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. Solv images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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.

Requests Breakdown

We found no issues to fix!

Requests Now

28

After Optimization

28

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Solv. According to our analytics all requests are already optimized.

Accessibility Review

solv.app accessibility score

77

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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

Heading elements are not in a sequentially-descending order

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

solv.app best practices score

92

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

Page has valid source maps

SEO Factors

solv.app SEO score

84

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Solv.app 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 Solv.app 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 description is not detected on the main page of Solv. 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: