Tools & Wizards About Us
lillyarch.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

lillyarch.com

Lilly Architects, Tulsa OK - Award Winning Tulsa Architects - 918.582.5044

Page Load Speed

1.2 sec in total

First Response

13 ms

Resources Loaded

966 ms

Page Rendered

198 ms

lillyarch.com screenshot

About Website

Click here to check amazing Lilly Arch content. Otherwise, check out these important facts you probably never knew about lillyarch.com

Lilly Architects, Tulsa OK - An award-winning, full-service, architecture, and interior design firm located in Tulsa, OK. Call (918) 582-5044

Visit lillyarch.com

Key Findings

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

Performance Metrics

lillyarch.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

lillyarch.com

13 ms

www.lillyarch.com

699 ms

style.min.css

10 ms

styles.css

33 ms

reset.css

33 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 92% of them (35 requests) were addressed to the original Lillyarch.com, 3% (1 request) were made to Fonts.googleapis.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (699 ms) belongs to the original domain Lillyarch.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.8 kB (1%)

Content Size

7.1 MB

After Optimization

7.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 23.4 kB

  • Original 30.2 kB
  • After minification 29.6 kB
  • After compression 6.8 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 23.4 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 52.8 kB

  • Original 7.0 MB
  • After minification 6.9 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. Lilly Arch images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 18.6 kB

  • Original 83.0 kB
  • After minification 83.0 kB
  • After compression 64.4 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 18.6 kB or 22% of the original size.

CSS Optimization

-21%

Potential reduce by 6.0 kB

  • Original 28.4 kB
  • After minification 28.4 kB
  • After compression 22.4 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. Lillyarch.com needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (57%)

Requests Now

35

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lillyarch.com

lillyarch.com

13 ms

www.lillyarch.com

www.lillyarch.com

699 ms

style.min.css

style.min.css

10 ms

styles.css

styles.css

33 ms

reset.css

reset.css

33 ms

fonts.css

fonts.css

31 ms

css

css

57 ms

animations.css

animations.css

70 ms

style.css

style.css

83 ms

single.css

single.css

71 ms

jquery.min.js

jquery.min.js

50 ms

js

js

125 ms

comment-reply.min.js

comment-reply.min.js

37 ms

hooks.min.js

hooks.min.js

36 ms

i18n.min.js

i18n.min.js

39 ms

index.js

index.js

46 ms

index.js

index.js

43 ms

hoverIntent.min.js

hoverIntent.min.js

44 ms

skrollr.min.js

skrollr.min.js

44 ms

imagesloaded.min.js

imagesloaded.min.js

48 ms

masonry.min.js

masonry.min.js

47 ms

rotator.js

rotator.js

175 ms

scripts.js

scripts.js

163 ms

logo-nb.svg

logo-nb.svg

6 ms

SS_20190705_8503539_H-2000x1333.jpg

SS_20190705_8503539_H-2000x1333.jpg

43 ms

SS_20190402_Front-Desk_001_H-2000x1333.jpg

SS_20190402_Front-Desk_001_H-2000x1333.jpg

44 ms

SS_20180507_8500706_H-2000x1333.jpg

SS_20180507_8500706_H-2000x1333.jpg

42 ms

Fox-Building-v2.jpg

Fox-Building-v2.jpg

65 ms

OKPOP_Exterior-Rendering_20180706_H-2000x1125.jpg

OKPOP_Exterior-Rendering_20180706_H-2000x1125.jpg

48 ms

Header-Image-36-Degrees-North-2000x1392.jpg

Header-Image-36-Degrees-North-2000x1392.jpg

49 ms

36dg-hi-res.jpg

36dg-hi-res.jpg

94 ms

Header-Image-Archer-Building-1-2000x1234.jpg

Header-Image-Archer-Building-1-2000x1234.jpg

62 ms

Header-Image-Lone-Wolf-2000x1333.jpg

Header-Image-Lone-Wolf-2000x1333.jpg

66 ms

CHROMA-161026-27063-2000x1333.jpg

CHROMA-161026-27063-2000x1333.jpg

92 ms

facebook.svg

facebook.svg

67 ms

instagram.svg

instagram.svg

70 ms

Swis721_Cn_BT_Roman.woff

Swis721_Cn_BT_Roman.woff

4 ms

mobile.css

mobile.css

51 ms

Accessibility Review

lillyarch.com accessibility score

54

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

lillyarch.com best practices score

83

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

SEO Factors

lillyarch.com SEO score

93

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

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

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

lillyarch.com

Open Graph data is detected on the main page of Lilly Arch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: