Tools & Wizards About Us
what-franchise.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

what-franchise.com

Franchise Opportunities UK - Business Franchises for Sale | What-Franchise.com

Page Load Speed

2.5 sec in total

First Response

245 ms

Resources Loaded

2.1 sec

Page Rendered

144 ms

what-franchise.com screenshot

About Website

Visit what-franchise.com now to see the best up-to-date What Franchise content for United Kingdom and also check out these interesting facts you probably never knew about what-franchise.com

Discover hundreds of different franchises on What Franchise. Choose from the most profitable franchises in the UK and find the perfect opportunity.

Visit what-franchise.com

Key Findings

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

Performance Metrics

what-franchise.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.375

28/100

15%

TTI (Time to Interactive)

Value24.5 s

0/100

10%

Network Requests Diagram

what-franchise.com

245 ms

what-franchise.com

336 ms

www.what-franchise.com

591 ms

6ee36ee2-fa94-4556-aa7e-e32751304035

507 ms

C0001.js

158 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 69% of them (24 requests) were addressed to the original What-franchise.com, 9% (3 requests) were made to Cdn.what-franchise.com and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (591 ms) belongs to the original domain What-franchise.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 412.2 kB (64%)

Content Size

647.5 kB

After Optimization

235.3 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-76%

Potential reduce by 87.3 kB

  • Original 115.0 kB
  • After minification 92.9 kB
  • After compression 27.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 22.1 kB, which is 19% 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 87.3 kB or 76% of the original size.

Image Optimization

-26%

Potential reduce by 739 B

  • Original 2.8 kB
  • After minification 2.1 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. Obviously, What Franchise needs image optimization as it can save up to 739 B or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-61%

Potential reduce by 324.2 kB

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

Requests Breakdown

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

Requests Now

27

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

what-franchise.com

what-franchise.com

245 ms

what-franchise.com

what-franchise.com

336 ms

www.what-franchise.com

www.what-franchise.com

591 ms

6ee36ee2-fa94-4556-aa7e-e32751304035

6ee36ee2-fa94-4556-aa7e-e32751304035

507 ms

C0001.js

C0001.js

158 ms

C0002.js

C0002.js

234 ms

C0003.js

C0003.js

238 ms

C0004.js

C0004.js

247 ms

C0005.js

C0005.js

247 ms

webfont.js

webfont.js

27 ms

gpt.js

gpt.js

47 ms

js

js

59 ms

st.js

st.js

405 ms

723.99cc3f026fd15def1055.min.js

723.99cc3f026fd15def1055.min.js

324 ms

646.9ed2b9b7a63bc7905d10.min.js

646.9ed2b9b7a63bc7905d10.min.js

398 ms

372.4288f3d78eaa91bc17ac.min.js

372.4288f3d78eaa91bc17ac.min.js

322 ms

714.f429894be08f7fcbd484.min.js

714.f429894be08f7fcbd484.min.js

336 ms

homepage.d0100df0954b249524cb.min.js

homepage.d0100df0954b249524cb.min.js

337 ms

459.f9ba14cd64c16bde5737.css

459.f9ba14cd64c16bde5737.css

406 ms

homepage.c647960b0467eedab3bb.css

homepage.c647960b0467eedab3bb.css

407 ms

gtm.js

gtm.js

100 ms

facebook-colour.png

facebook-colour.png

417 ms

twitter-colour.png

twitter-colour.png

422 ms

linkedin-colour.png

linkedin-colour.png

422 ms

pubads_impl.js

pubads_impl.js

65 ms

search-svg.svg

search-svg.svg

352 ms

fontawesome.min.css

fontawesome.min.css

144 ms

solid.min.css

solid.min.css

142 ms

brands.min.css

brands.min.css

143 ms

Merriweather-Light.ttf

Merriweather-Light.ttf

173 ms

Merriweather-Bold.ttf

Merriweather-Bold.ttf

182 ms

DMSans-Regular.ttf

DMSans-Regular.ttf

182 ms

DMSans-Bold.ttf

DMSans-Bold.ttf

252 ms

container.html

container.html

34 ms

fa-solid-900.woff

fa-solid-900.woff

246 ms

Accessibility Review

what-franchise.com accessibility score

79

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

Image elements do not have [alt] attributes

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

what-franchise.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

what-franchise.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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 What-franchise.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 What-franchise.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

what-franchise.com

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