Tools & Wizards About Us
apiline.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

apiline.com

Home - API Promotional Products

Page Load Speed

1.1 sec in total

First Response

245 ms

Resources Loaded

703 ms

Page Rendered

110 ms

apiline.com screenshot

About Website

Click here to check amazing API Line content. Otherwise, check out these important facts you probably never knew about apiline.com

Apothecary Products LLC from Burnsville MN USA Looking for promotional products, advertising specialties and business gifts? You've come to the right site! Whether you are looking for a specific i...

Visit apiline.com

Key Findings

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

Performance Metrics

apiline.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.382

27/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

apiline.com

245 ms

jQueryScriptCombiner.ashx

62 ms

angular.min.js

99 ms

application.min.js

50 ms

font-awesome.min.css

123 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 64% of them (58 requests) were addressed to the original Apiline.com, 13% (12 requests) were made to Cdnjs.cloudflare.com and 13% (12 requests) were made to Commonmedia.asicentral.com. The less responsive or slowest element that took the longest time to load (245 ms) belongs to the original domain Apiline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.1 kB (13%)

Content Size

702.2 kB

After Optimization

612.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 66.5 kB

  • Original 90.6 kB
  • After minification 88.5 kB
  • After compression 24.2 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 66.5 kB or 73% of the original size.

Image Optimization

-5%

Potential reduce by 10.4 kB

  • Original 206.9 kB
  • After minification 196.5 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. API Line images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 6.4 kB

  • Original 337.8 kB
  • After minification 337.8 kB
  • After compression 331.5 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

-10%

Potential reduce by 6.9 kB

  • Original 66.8 kB
  • After minification 66.6 kB
  • After compression 59.9 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. Apiline.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 72 (80%)

Requests Now

90

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

apiline.com

apiline.com

245 ms

jQueryScriptCombiner.ashx

jQueryScriptCombiner.ashx

62 ms

angular.min.js

angular.min.js

99 ms

application.min.js

application.min.js

50 ms

font-awesome.min.css

font-awesome.min.css

123 ms

toastr.min.css

toastr.min.css

121 ms

Core.min.js

Core.min.js

35 ms

ScriptConstants.ashx

ScriptConstants.ashx

36 ms

angular-recaptcha.js

angular-recaptcha.js

35 ms

cookieconsent.min.js

cookieconsent.min.js

42 ms

google-translator.css

google-translator.css

54 ms

cookieconsent.min.css

cookieconsent.min.css

54 ms

reset.css

reset.css

54 ms

text.css

text.css

56 ms

960-mobile.css

960-mobile.css

60 ms

jquery-ui.css

jquery-ui.css

117 ms

universal30.css

universal30.css

116 ms

universal30-mobile.css

universal30-mobile.css

117 ms

lgml20.css

lgml20.css

117 ms

ui-select.css

ui-select.css

119 ms

angular-block-ui.min.css

angular-block-ui.min.css

137 ms

application.min.css

application.min.css

145 ms

NewsletterSignup-mobile.css

NewsletterSignup-mobile.css

145 ms

SocialLinks.css

SocialLinks.css

145 ms

SocialFeed.css

SocialFeed.css

144 ms

Content-mobile.css

Content-mobile.css

151 ms

Logo.css

Logo.css

152 ms

Logo-mobile.css

Logo-mobile.css

175 ms

EndUserStatus.css

EndUserStatus.css

177 ms

ShoppingCart.css

ShoppingCart.css

174 ms

ShoppingCart-mobile.css

ShoppingCart-mobile.css

177 ms

Address.css

Address.css

177 ms

Address-mobile.css

Address-mobile.css

177 ms

QuickSearchBasic.css

QuickSearchBasic.css

179 ms

QuickSearchBasic-mobile.css

QuickSearchBasic-mobile.css

178 ms

Menu.css

Menu.css

184 ms

Menu-mobile.css

Menu-mobile.css

184 ms

Banner.css

Banner.css

185 ms

Banner-mobile.css

Banner-mobile.css

185 ms

60.css

60.css

54 ms

font.css

font.css

44 ms

js

js

149 ms

element.js

element.js

148 ms

angular-ui-router.min.js

angular-ui-router.min.js

139 ms

angular-resource.min.js

angular-resource.min.js

168 ms

angular-cookies.min.js

angular-cookies.min.js

148 ms

ui-bootstrap-tpls.min.js

ui-bootstrap-tpls.min.js

175 ms

bootstrap-notify.min.js

bootstrap-notify.min.js

172 ms

toastr.min.js

toastr.min.js

172 ms

angular-translate.min.js

angular-translate.min.js

168 ms

angular-translate-loader-partial.min.js

angular-translate-loader-partial.min.js

172 ms

angular-translate-storage-cookie.min.js

angular-translate-storage-cookie.min.js

173 ms

angular-translate-storage-local.min.js

angular-translate-storage-local.min.js

173 ms

angular-translate-handler-log.min.js

angular-translate-handler-log.min.js

181 ms

ProductOfTheDay.css

ProductOfTheDay.css

181 ms

ProductSetAutoUpdate.css

ProductSetAutoUpdate.css

156 ms

ProductSetAutoUpdate-mobile.css

ProductSetAutoUpdate-mobile.css

156 ms

WebResource.axd

WebResource.axd

188 ms

ScriptResource.axd

ScriptResource.axd

180 ms

jquery.fitvids.js

jquery.fitvids.js

146 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

143 ms

Common.min.js

Common.min.js

143 ms

SocialFeed.js

SocialFeed.js

146 ms

Address.js

Address.js

144 ms

Menu.js

Menu.js

116 ms

Menu-mobile.js

Menu-mobile.js

116 ms

jquery.lazyloadVS.min.js

jquery.lazyloadVS.min.js

98 ms

jquery.carousel.js

jquery.carousel.js

97 ms

ProductSetAutoUpdate.js

ProductSetAutoUpdate.js

151 ms

Video.js

Video.js

151 ms

google-translator.js

google-translator.js

137 ms

vendor-bundle.min.js

vendor-bundle.min.js

155 ms

bg-body.gif

bg-body.gif

20 ms

20241934.jpg

20241934.jpg

227 ms

AlertIcons-Warning.png

AlertIcons-Warning.png

98 ms

logo.png

logo.png

203 ms

widgets.js

widgets.js

155 ms

messageIcons.png

messageIcons.png

154 ms

bg-header.jpg

bg-header.jpg

154 ms

logo.png

logo.png

131 ms

search-bg-left.png

search-bg-left.png

145 ms

search-bg-right.png

search-bg-right.png

153 ms

btn-go.png

btn-go.png

150 ms

bg-main.gif

bg-main.gif

150 ms

bg-footerRepeat.png

bg-footerRepeat.png

153 ms

bg-footer.png

bg-footer.png

157 ms

iframe_api

iframe_api

175 ms

block-ui-overlay.view.html

block-ui-overlay.view.html

54 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

31 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

53 ms

www-widgetapi.js

www-widgetapi.js

17 ms

Accessibility Review

apiline.com accessibility score

88

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 progressbar elements do not have accessible names.

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

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

Page has valid source maps

SEO Factors

apiline.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 Apiline.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 Apiline.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

apiline.com

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