Tools & Wizards About Us
franpos.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

franpos.com

Page Load Speed

3.1 sec in total

First Response

475 ms

Resources Loaded

2.3 sec

Page Rendered

306 ms

franpos.com screenshot

About Website

Visit franpos.com now to see the best up-to-date Franpos content for United States and also check out these interesting facts you probably never knew about franpos.com

Visit franpos.com

Key Findings

We analyzed Franpos.com page load time and found that the first response time was 475 ms and then it took 2.6 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

franpos.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value440 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value1.514

0/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

franpos.com

475 ms

css

35 ms

wpp.min.js

54 ms

frontend.min.css

111 ms

flatpickr.min.css

155 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 87% of them (86 requests) were addressed to the original Franpos.com, 5% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to W2.franpos.com. The less responsive or slowest element that took the longest time to load (648 ms) belongs to the original domain Franpos.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.3 kB (9%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Franpos.com main page is 1.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 851.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 80.8 kB

  • Original 100.1 kB
  • After minification 92.8 kB
  • After compression 19.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 80.8 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 37.2 kB

  • Original 851.7 kB
  • After minification 814.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. Franpos images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 6.4 kB

  • Original 491.8 kB
  • After minification 491.8 kB
  • After compression 485.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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 20.9 kB

  • Original 198.3 kB
  • After minification 182.8 kB
  • After compression 177.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. Franpos.com needs all CSS files to be minified and compressed as it can save up to 20.9 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (64%)

Requests Now

80

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

franpos.com

franpos.com

475 ms

css

css

35 ms

wpp.min.js

wpp.min.js

54 ms

frontend.min.css

frontend.min.css

111 ms

flatpickr.min.css

flatpickr.min.css

155 ms

select2.min.css

select2.min.css

156 ms

dashicons.min.css

dashicons.min.css

156 ms

wpp.css

wpp.css

158 ms

style.css

style.css

160 ms

fonts.css

fonts.css

163 ms

bootstrap-grid.min.css

bootstrap-grid.min.css

208 ms

fontawesome-all.css

fontawesome-all.css

209 ms

screen.css

screen.css

214 ms

responsive.css

responsive.css

211 ms

owl.carousel.css

owl.carousel.css

213 ms

slick.css

slick.css

218 ms

swiper.min.css

swiper.min.css

262 ms

shadowbox.css

shadowbox.css

260 ms

elementor-icons.min.css

elementor-icons.min.css

262 ms

custom-frontend.min.css

custom-frontend.min.css

270 ms

post-4231.css

post-4231.css

283 ms

custom-pro-frontend.min.css

custom-pro-frontend.min.css

289 ms

all.min.css

all.min.css

316 ms

v4-shims.min.css

v4-shims.min.css

313 ms

global.css

global.css

318 ms

post-5.css

post-5.css

323 ms

post-5578.css

post-5578.css

326 ms

jquery.min.js

jquery.min.js

345 ms

jquery-migrate.min.js

jquery-migrate.min.js

366 ms

flatpickr.min.js

flatpickr.min.js

369 ms

select2.min.js

select2.min.js

371 ms

jquery-2.2.4.js

jquery-2.2.4.js

436 ms

owl.carousel.js

owl.carousel.js

381 ms

slick.js

slick.js

400 ms

plugin.js

plugin.js

528 ms

script.js

script.js

433 ms

v4-shims.min.js

v4-shims.min.js

422 ms

86b9e51bcce44fe18f082c8b194b9d7c.js

86b9e51bcce44fe18f082c8b194b9d7c.js

28 ms

frontend.min.js

frontend.min.js

433 ms

shadowbox.js

shadowbox.js

407 ms

hoverIntent.min.js

hoverIntent.min.js

364 ms

maxmegamenu.js

maxmegamenu.js

337 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

337 ms

webpack.runtime.min.js

webpack.runtime.min.js

336 ms

frontend-modules.min.js

frontend-modules.min.js

359 ms

hooks.min.js

hooks.min.js

485 ms

i18n.min.js

i18n.min.js

484 ms

frontend.min.js

frontend.min.js

437 ms

waypoints.min.js

waypoints.min.js

436 ms

core.min.js

core.min.js

435 ms

frontend.min.js

frontend.min.js

430 ms

elements-handlers.min.js

elements-handlers.min.js

430 ms

heap-8926350.js

heap-8926350.js

261 ms

inc-img.png

inc-img.png

576 ms

today-img.png

today-img.png

576 ms

silicon-img.png

silicon-img.png

577 ms

business-img.png

business-img.png

575 ms

trends-img.png

trends-img.png

575 ms

logo_APPA_master-1.png

logo_APPA_master-1.png

575 ms

brand.png

brand.png

255 ms

img-pet-01.png

img-pet-01.png

256 ms

ecommerce-app.png

ecommerce-app.png

502 ms

img-beauty-salon2-01.png

img-beauty-salon2-01.png

337 ms

img-restaurant-01.png

img-restaurant-01.png

336 ms

Pink-Cart.png

Pink-Cart.png

254 ms

Shopping-Cart.png

Shopping-Cart.png

337 ms

Blue-Scissors.png

Blue-Scissors.png

337 ms

Scissors.png

Scissors.png

337 ms

Gold-Tray-1.png

Gold-Tray-1.png

500 ms

Tray.png

Tray.png

500 ms

runza-img.png

runza-img.png

499 ms

planet-img.png

planet-img.png

499 ms

Menchies_Frozen_Yogurt_logo-1.png

Menchies_Frozen_Yogurt_logo-1.png

499 ms

cropped-cropped-cropped-cropped-20161025_PC_LogoRGB-p3xmoj2dqvmeotoo614tg06c4jui7la5cy8r6vfev4-p6m9s2p3062ihgmygyzqe814yamzs9cryqrtjxn6yo-1.png

cropped-cropped-cropped-cropped-20161025_PC_LogoRGB-p3xmoj2dqvmeotoo614tg06c4jui7la5cy8r6vfev4-p6m9s2p3062ihgmygyzqe814yamzs9cryqrtjxn6yo-1.png

573 ms

woofgang.png

woofgang.png

574 ms

top_arrow.png

top_arrow.png

572 ms

International-Franchise-Association.png

International-Franchise-Association.png

573 ms

Muli-Regular.woff

Muli-Regular.woff

572 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

253 ms

Muli-Light.woff

Muli-Light.woff

572 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf

254 ms

Muli-ExtraLight.woff

Muli-ExtraLight.woff

624 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFlOkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFlOkEk30e0.ttf

336 ms

Muli-SemiBold.woff

Muli-SemiBold.woff

624 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e0.ttf

336 ms

Muli-Bold.woff

Muli-Bold.woff

624 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

336 ms

Muli-ExtraBold.woff

Muli-ExtraBold.woff

623 ms

Muli-Black.woff

Muli-Black.woff

622 ms

bg_section.png

bg_section.png

589 ms

bg_1.png

bg_1.png

648 ms

proximanova-regular-webfont.woff

proximanova-regular-webfont.woff

585 ms

proximanova-bold-webfont.woff

proximanova-bold-webfont.woff

589 ms

WebsiteAutomation.js

WebsiteAutomation.js

544 ms

fa-brands-400.woff

fa-brands-400.woff

418 ms

fa-solid-900.woff

fa-solid-900.woff

419 ms

fa-regular-400.woff

fa-regular-400.woff

419 ms

h

h

167 ms

WebsiteAutomation.js

WebsiteAutomation.js

307 ms

Accessibility Review

franpos.com accessibility score

80

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

Document doesn't have a <title> element

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.

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

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

SEO Factors

franpos.com SEO score

67

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

Document doesn't have a <title> element

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

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

franpos.com

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