Tools & Wizards About Us
saffire.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

saffire.com

Website Ticketing for Events, Fairs, Festivals & More | Saffire

Page Load Speed

3.1 sec in total

First Response

631 ms

Resources Loaded

2.2 sec

Page Rendered

302 ms

saffire.com screenshot

About Website

Welcome to saffire.com homepage info - get ready to check Saffire best content for United States right away, or after learning these important things about saffire.com

Saffire empowers hundreds of events with the industry’s only fully integrated ticketing and website platform. You get a beautiful, unique and engaging website fully equipped with SaffireTix® to manage...

Visit saffire.com

Key Findings

We analyzed Saffire.com page load time and found that the first response time was 631 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

saffire.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.1 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

Network Requests Diagram

www.saffire.com

631 ms

gtm.js

89 ms

fbevents.js

37 ms

basic.css

191 ms

standard.css

388 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 46% of them (35 requests) were addressed to the original Saffire.com, 21% (16 requests) were made to Cdn.saffire.com and 8% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (876 ms) belongs to the original domain Saffire.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 726.8 kB (50%)

Content Size

1.5 MB

After Optimization

730.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Saffire.com main page is 1.5 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. 70% of websites need less resources to load. Javascripts take 998.3 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 61.8 kB

  • Original 90.1 kB
  • After minification 86.3 kB
  • After compression 28.3 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 61.8 kB or 69% of the original size.

Image Optimization

-5%

Potential reduce by 3.6 kB

  • Original 69.7 kB
  • After minification 66.2 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. Saffire images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 457.6 kB

  • Original 998.3 kB
  • After minification 915.8 kB
  • After compression 540.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 457.6 kB or 46% of the original size.

CSS Optimization

-68%

Potential reduce by 203.8 kB

  • Original 299.5 kB
  • After minification 298.8 kB
  • After compression 95.7 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. Saffire.com needs all CSS files to be minified and compressed as it can save up to 203.8 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (79%)

Requests Now

68

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.saffire.com

www.saffire.com

631 ms

gtm.js

gtm.js

89 ms

fbevents.js

fbevents.js

37 ms

basic.css

basic.css

191 ms

standard.css

standard.css

388 ms

redactor.css

redactor.css

362 ms

responsiveNav.css

responsiveNav.css

395 ms

mobile-nav.css

mobile-nav.css

262 ms

main-cfv.css

main-cfv.css

351 ms

theme.css

theme.css

134 ms

WebResource.axd

WebResource.axd

201 ms

ScriptResource.axd

ScriptResource.axd

375 ms

ScriptResource.axd

ScriptResource.axd

297 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

451 ms

jquery-ui-1.10.1.custom.min.js

jquery-ui-1.10.1.custom.min.js

573 ms

jquery-mobile-1.4.5.min.js

jquery-mobile-1.4.5.min.js

392 ms

modernizr.custom.88772.js

modernizr.custom.88772.js

517 ms

lozad.min.js

lozad.min.js

398 ms

idangerous.swiper-desktop.js

idangerous.swiper-desktop.js

501 ms

swiper-4.5.1.min.js

swiper-4.5.1.min.js

562 ms

simplebar.min.js

simplebar.min.js

485 ms

functions.js

functions.js

559 ms

json2.js

json2.js

602 ms

webcam.min.js

webcam.min.js

603 ms

angular.js

angular.js

833 ms

angular-animate.js

angular-animate.js

656 ms

angular-touch.min.js

angular-touch.min.js

653 ms

angular-sanitize.js

angular-sanitize.js

688 ms

angular-cookies.js

angular-cookies.js

676 ms

ngMask.min.js

ngMask.min.js

699 ms

app.js

app.js

745 ms

cardWidget.js

cardWidget.js

758 ms

owl.carousel.min.js

owl.carousel.min.js

780 ms

cssScroller.js

cssScroller.js

783 ms

instafeed.js

instafeed.js

788 ms

theme.js

theme.js

61 ms

js

js

24 ms

anythingslider.css

anythingslider.css

876 ms

conversion.js

conversion.js

111 ms

cookie-js

cookie-js

876 ms

css2

css2

35 ms

images.ashx

images.ashx

24 ms

images.ashx

images.ashx

104 ms

images.ashx

images.ashx

135 ms

images.ashx

images.ashx

150 ms

images.ashx

images.ashx

124 ms

images.ashx

images.ashx

149 ms

images.ashx

images.ashx

146 ms

WidgetScript

WidgetScript

23 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

24 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

77 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

58 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

58 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

59 ms

logo.png

logo.png

435 ms

wlw4

wlw4

251 ms

demo-title.png

demo-title.png

117 ms

content-block-bg.png

content-block-bg.png

58 ms

bg-footer.jpg

bg-footer.jpg

131 ms

flame-footer-abstract.png

flame-footer-abstract.png

435 ms

footer-signup-icon.png

footer-signup-icon.png

365 ms

logo-footer.png

logo-footer.png

185 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

166 ms

69 ms

insight.min.js

insight.min.js

42 ms

sdk.js

sdk.js

18 ms

sdk.js

sdk.js

6 ms

insight_tag_errors.gif

insight_tag_errors.gif

46 ms

36 ms

bootstrap.min.css

bootstrap.min.css

26 ms

jquery.min.js

jquery.min.js

34 ms

piUtils.js

piUtils.js

19 ms

bootstrap.min.js

bootstrap.min.js

43 ms

css2

css2

17 ms

pd.js

pd.js

4 ms

Accessibility Review

saffire.com accessibility score

85

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.

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

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

High

Links do not have a discernible name

Best Practices

saffire.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

saffire.com SEO score

86

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

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

saffire.com

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