Tools & Wizards About Us
torosi.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

torosi.com

The Official Torosi | Engagement Rings & Bands Handcrafted in California

Page Load Speed

3.2 sec in total

First Response

164 ms

Resources Loaded

2.6 sec

Page Rendered

438 ms

torosi.com screenshot

About Website

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

Torosi | Engagement Rings & Wedding Bands | Shop Online & Browse the Official Torosi Collections | Embrace the Look of Brilliance & Find your Perfect Piece!

Visit torosi.com

Key Findings

We analyzed Torosi.com page load time and found that the first response time was 164 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

torosi.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value2,760 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.423

23/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

torosi.com

164 ms

www.torosi.com

138 ms

www.torosi.com

503 ms

font-awesome.min.css

38 ms

jquery.fancybox.css

71 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 81% of them (94 requests) were addressed to the original Torosi.com, 3% (4 requests) were made to Google-analytics.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (989 ms) belongs to the original domain Torosi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.0 kB (6%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Torosi.com main page is 2.0 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 89.1 kB

  • Original 101.7 kB
  • After minification 61.2 kB
  • After compression 12.7 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 40.5 kB, which is 40% 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 89.1 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 29.6 kB

  • Original 1.7 MB
  • After minification 1.6 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. Torosi images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 12.6 kB

  • Original 200.7 kB
  • After minification 200.7 kB
  • After compression 188.1 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

-1%

Potential reduce by 707 B

  • Original 93.7 kB
  • After minification 93.7 kB
  • After compression 93.0 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. Torosi.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (44%)

Requests Now

109

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

torosi.com

torosi.com

164 ms

www.torosi.com

www.torosi.com

138 ms

www.torosi.com

www.torosi.com

503 ms

font-awesome.min.css

font-awesome.min.css

38 ms

jquery.fancybox.css

jquery.fancybox.css

71 ms

owl.carousel.min.css

owl.carousel.min.css

139 ms

owl.theme.default.min.css

owl.theme.default.min.css

201 ms

main.css

main.css

340 ms

jquery.js

jquery.js

266 ms

jquerypp.custom.js

jquerypp.custom.js

201 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

201 ms

access_logs.js

access_logs.js

203 ms

global.js

global.js

268 ms

bootstrap.min.js

bootstrap.min.js

269 ms

bootstrap-collapse.js

bootstrap-collapse.js

266 ms

bootstrap-dropdown.js

bootstrap-dropdown.js

270 ms

jquery.elastislide.js

jquery.elastislide.js

334 ms

angular.js

angular.js

431 ms

angular-store-mini.js

angular-store-mini.js

334 ms

ngCompare.js

ngCompare.js

334 ms

ngRecentlyViewed.js

ngRecentlyViewed.js

369 ms

auth.js

auth.js

431 ms

mwheelIntent.js

mwheelIntent.js

434 ms

jquery.mousewheel.js

jquery.mousewheel.js

434 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

431 ms

bigSlide.min.js

bigSlide.min.js

432 ms

jquery.threesixty.js

jquery.threesixty.js

487 ms

owl.carousel.min.js

owl.carousel.min.js

490 ms

home.js

home.js

490 ms

api.js

api.js

44 ms

css

css

48 ms

analytics.js

analytics.js

91 ms

3000644_1.jpg

3000644_1.jpg

205 ms

3000644_0.png

3000644_0.png

89 ms

3000645_1.jpg

3000645_1.jpg

205 ms

3000645_0.png

3000645_0.png

205 ms

3000646_1.jpg

3000646_1.jpg

205 ms

3000646_0.png

3000646_0.png

205 ms

3000647_1.jpg

3000647_1.jpg

282 ms

3000647_0.png

3000647_0.png

286 ms

logo-white.png

logo-white.png

284 ms

3000091_0.png

3000091_0.png

282 ms

3000092_0.png

3000092_0.png

283 ms

3000093_0.png

3000093_0.png

285 ms

3000513_0.png

3000513_0.png

333 ms

3000543_0.png

3000543_0.png

332 ms

3000605_0.png

3000605_0.png

333 ms

3000606_0.png

3000606_0.png

332 ms

3000607_0.png

3000607_0.png

335 ms

3000609_0.png

3000609_0.png

369 ms

3000610_0.png

3000610_0.png

409 ms

3000097_0.png

3000097_0.png

408 ms

3000096_0.png

3000096_0.png

409 ms

3000099_0.png

3000099_0.png

407 ms

3000101_0.png

3000101_0.png

409 ms

3000514_0.png

3000514_0.png

422 ms

3000098_0.png

3000098_0.png

463 ms

3000100_0.png

3000100_0.png

467 ms

3000103_0.png

3000103_0.png

466 ms

gtm.js

gtm.js

199 ms

273801823

273801823

407 ms

3000102_0.png

3000102_0.png

449 ms

3000515_0.png

3000515_0.png

450 ms

3000587_0.png

3000587_0.png

455 ms

3000588_0.png

3000588_0.png

505 ms

3000589_0.png

3000589_0.png

508 ms

3000590_0.png

3000590_0.png

473 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

24 ms

nexa-book-webfont.woff

nexa-book-webfont.woff

455 ms

trajanpro-regular.woff

trajanpro-regular.woff

581 ms

3000591_0.png

3000591_0.png

465 ms

3000533_0.png

3000533_0.png

512 ms

collect

collect

32 ms

access_logs.php

access_logs.php

514 ms

json.php

json.php

989 ms

3000534_0.png

3000534_0.png

403 ms

3000535_0.png

3000535_0.png

403 ms

3000592_0.png

3000592_0.png

403 ms

destination

destination

59 ms

a414c3bc-a583-461c-9e1f-6d71a36ed6d2.js

a414c3bc-a583-461c-9e1f-6d71a36ed6d2.js

350 ms

fbevents.js

fbevents.js

76 ms

core.js

core.js

75 ms

5083588.js

5083588.js

158 ms

collect

collect

27 ms

3000593_0.png

3000593_0.png

389 ms

logo.png

logo.png

389 ms

3000662_0.jpg

3000662_0.jpg

643 ms

3000662_1.jpg

3000662_1.jpg

579 ms

3000650_0.png

3000650_0.png

453 ms

3000649_0.png

3000649_0.png

450 ms

collect

collect

103 ms

js

js

68 ms

3000648_0.png

3000648_0.png

452 ms

3000660_0.jpg

3000660_0.jpg

535 ms

3000660_1.jpg

3000660_1.jpg

473 ms

3000675_0.jpg

3000675_0.jpg

518 ms

3000675_1.jpg

3000675_1.jpg

537 ms

diamond

diamond

972 ms

3000665_0.jpg

3000665_0.jpg

520 ms

3000665_1.jpg

3000665_1.jpg

527 ms

3000658_0.jpg

3000658_0.jpg

529 ms

3000658_1.jpg

3000658_1.jpg

584 ms

3000659_0.jpg

3000659_0.jpg

579 ms

banner.js

banner.js

144 ms

5083588.js

5083588.js

94 ms

collectedforms.js

collectedforms.js

50 ms

fb.js

fb.js

48 ms

3000659_1.jpg

3000659_1.jpg

578 ms

Newsletter-Button-b.png

Newsletter-Button-b.png

543 ms

relatedBg.jpg

relatedBg.jpg

595 ms

diamond-outline.png

diamond-outline.png

596 ms

tsub2.png

tsub2.png

602 ms

round-top.png

round-top.png

604 ms

round-side.png

round-side.png

655 ms

collect

collect

13 ms

collect

collect

12 ms

Accessibility Review

torosi.com accessibility score

64

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

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

High

Links do not have a discernible name

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.

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

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

High

Page has valid source maps

SEO Factors

torosi.com SEO score

74

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torosi.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Torosi.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

torosi.com

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